When developing App Actions, you might encounter issues with your setup or with the App Actions test tool. This page describes some commonly encountered issues and their fixes.
Error: "No App found to open URL" appears in a toast notification
Check your fulfillment
urlTemplate in your
actions.xml to make sure it's
configured correctly. If using App Links URLs, ensure you can trigger your URL
ACTION_VIEW and the URL. If using intent-based URLs, ensure
your Activity is correctly configured to start using the provided parameters.
Error: "App isn't installed"
This error may mean that the
<intent-filter> in your
file doesn't filter the deep link that you specified in your
Make sure you check this first before filing a bug.
Error: "An entity set reference containing neither an entity set ID nor a URL filter was found." appears in Android Studio
This condition is caused by a known linter issue for the
<entity-set-reference> tag. You can safely ignore this message. As a
workaround, you can disable lint check for this tag by adding the
tools:ignore="ValidActionsXml" attribute to it.
Here's an example of an entity set reference with a disabled lint check:
<entity-set-reference entitySetId="example" tools:ignore="ValidActionsXml" />
Error: "Invalid location" for actions schema document when uploading APK
Your APK upload may fail if you use an obfuscation or optimization tool that affects resources for your release APK. Tools like ProGuard that avoid resource files do not cause this issue.
To resolve this issue, try disabling the tool for your app's
file (for example, by using an allowlist).
The "Accept" button on Play Terms of Service form is disabled.
This might mean that the signed in user doesn't have the required access level to accept those terms. Make sure the first submission is done by the administrator of the Play Console profile.
App Actions test tool
Before attempting any of the following fixes, update your installation of the App Actions test tool to the most recent version.
The App Actions test tool plugin cannot locate my
Ensure you have added the correct
<meta-data> tag in your
My App Action preview doesn't match my current
Your preview does not update itself dynamically with the content of your
actions.xml file. After you change your
actions.xml file manually or after
switching build variants in Android Studio, save your
actions.xml file and
click Update Preview in the test tool.
The App Actions test tool plugin stopped working or is generating errors.
First, make sure you've updated Android Studio to the latest version. If you are getting a 403 error, you also might be running the plugin on a package where you don't have permissions to run on.
If the error still persists, please file a bug and send the following details to Google:
- Details of the error dialog
- Android Studio Logs. Go to Help > Show Log in Finder. This shows you
the location of the
idea.login your Finder. Search for "Submit Actions Request Body:" in the log file, and paste the server responses (there should be two results for actions).
When invoking the App Action with the test plugin, the Assistant says, "Sorry, I couldn't find that."
Depending on your setup, this response may appear for different reasons. Try the following steps:
- Sign in to Android Studio, the Play Console, and your test device with the same Google account.
- Enable device data syncing.
- Set the device and Google Assistant language to
- Check that the package name of the application in the Google Play Console matches with the package name in the test application.
- In the fulfillment
urlTemplatedefinition in your
actions.xmlfile, make sure that the
android:schemevalues match what's declared in the
- Remove all previous installations of your app from your test device and install a fresh build.
- Delete the preview from App Actions test tool and create a new preview again.
- Use an Android physical device for testing.
- Check in the Logcat tool for failures related to fulfillment for Google Assistant. You should see an intent launched to your app.
- Enable the 'App info for your devices' setting for the account.
- Open Google Assistant and ensure you have completed setup. (Usually the setup progress bar appears as a blue bar at the bottom of the screen, but it may look different in some cases.)
- When using Google Assistant to trigger an App Action, make sure that the invocation name matches the preview created by the App Actions test tool.
- Try using text input instead of voice to avoid any transcription errors.
- Configure your test build so that the
applicationIdexactly matches an APK or AAB uploaded to the Google Play Console. Note that optional
applicationIdSuffixproperties can change the final
applicationIdof builds for certain product flavors and build variants. In this example, the
applicationIdfor the mock product flavor is
com.example.android.architecture.blueprints.master.mock, instead of
- Configure your preview to use a unique invocation name. Try using a unique word that reduces the chances for collision with other apps.
- To isolate issues when troubleshooting a shareable codebase, try running the the sample App Actions Fitness App. Make sure that the Fitness app works end-to-end. Then incrementally add additional features on top of this app to see if you can replicate issues.
- If using G Suite accounts, make sure Google Assistant is turned on by the administrator. We recommend creating a non-G Suite test account as a workaround and setting it up as a licensed tester through Play Store. From that account, testers should be able to create previews for their app and test using that account on their device successfully.
- If none of these steps work, raise a issue in the App Action issue tracker.