This page describes some commonly encountered issues and their fixes.
The App Actions test tool plugin cannot locate my actions.xml file.
Ensure you have added the correct meta-data tag in your
A toast notification appears with an error that the app cannot be run.
Check your fulfillment
urlTemplate in your
actions.xml to make sure it is
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.
The App Actions test tool plugin is crashing or I see an error.
Make sure you've updated Android Studio to the latest version.
If you are getting a 403 error, you 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).
I changed my actions.xml file and clicked Update Preview, but the preview is not updated.
Make sure to save your
actions.xml file before updating the preview.
I get an "App isn't installed" error.
This may mean that the
<intent-filter> in your
doesn't filter the deep link that you specified in your
actions.xml. Make sure
you check this first before filing a bug.
I see an Android Studio message that says urlFilter is required.
This is a known linter issue for the
<entity-set-reference> tag which we're
fixing. You can safely ignore this message. As a workaround, you can disable
lint check for this tag by adding the
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" />
I get an error that my actions schema document was given at an invalid location when uploading my 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
(for example, by using an allowlist).
"Accept" button on Play Terms of Service form is disabled
This may mean that the logged 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.