I developed an application with react-native and I add app actions to the application.
I followed instructions on docs and test the app by App Action Test Tools (AATT) and it worked pretty well (the invocation name is 'Test app').
After creating the preview for actions, I tried with google voice assistant directly (not just using AATT) and still it worked pretty well.
Right now I create a project in google play console with name 'MyApp' and create an Internal testing release and add another user as a tester and upload aab file for this release.
Finally I shared the google play link with tester user.
Tester user installed the app but actions doesn't work with google voice assistant!! I tried different commands, such as 'Hey google, search time in My App' and 'Hey google, search time in Test App' and etc. But non of them worked!
Do I need 'create preview' for Internal testing?
This step is not clear to me, what I need to do more to be sure the app will work with voice assistant without create preview by AATT?
I've successfully completed the publishing process for an APK to the Internal Test Track.
But when I try to view the App for download on the Google Play Store using the "VIEW ON GOOGLE PLAY" link in the screenshot below...
...it opens a new window with the following error:
I've also tried using the testers link "download it on Google Play." below...
...but it results in the same message stating the App can't be found.
This is the first time the App has been published and it's being done on the Internal Test Track.
The automated testing picked up a few warning and minor issues but no errors:
Has anyone experienced this issue before? I've contacted Google support for advice but I thought it would be worth trying here too and seeing if anyone had any suggestions on what to try next.
Thanks.
If this is the first time your app is being published on a track, it will take a couple of hours to be processed. This is only a one-time thing though, for future updates, the availability will be immediate on the internal test track.
Once the app is available, you'll also need to follow the opt-in link to be eligible for the download of the app.
Please delete cache and data of google play app on your device, then new updated version will be available
For Android App Bundles (AAB)
On the left menu, select Release > Devices and versions > App bundle
explorer.
Select the artifact filter near the top right of the page.
On the “Choose an artifact” table, select the right arrow on the
artifact you want to view.
Select the Downloads tab.
To share a link to install a specific APK: In the “Internal app
sharing link” section, select Copy shareable link.
As of today, the format of the shareable link:
https://play.google.com/apps/test/<package.name>/<version.number>
For Both APKs and AABs
You can use Internal app sharing instead.
Upload an APK or app bundle on the internal app sharing upload page
Then you can make your app available to anyone by sharing a download link.
Before anyone can download, they need to turn on internal app sharing on their Google Play Store app.
Open the Google Play Store app Google Play.
Tap Menu Menu > Settings.
In the “About” section, tap the Play Store version 7 times.
After the Internal app sharing setting appears, tap the switch to turn on
internal app sharing.
More information can be found here.
Answer for latest play console 2021
I was having same problem but since play console is lot different I didnt found any suitable solution but after trying a bit, this was solution that worked for me.
Play Console > Setup > Internal App Sharing > Email Lists > Make sure your email list is checked and saved.
In uploader and tester section make sure 'Anyone you shared link with can download' is selected.
Thats it.
I also created video on how this problem can be solved:
https://www.youtube.com/watch?v=gAiu76l4-7s
I just went through this completely unintuitive process, so let me clear up some myths:
Internal testing does NOT require the app be publicly released
The review process for your app apparently needs to complete before the app is available, as others pointed out, but the Play Console gives no indication this is a prerequisite, and happily states in several places that the App is available to internal testers when it is not. In my case the review took about a month to complete, which is why the "We are experiencing longer than normal review times" message was appearing in the console. This was the initial creation of my app, so I don't know which items-under-review were actually required, as the whole backlog completed at the same time (also with no notice to me).
Even at this point, if I follow the 'join' link on my phone, I still have the same issues the OP had. Clearing Play Store cache and other tricks did nothing. Instead, I had to click it from a PC, follow the prompts, and choose to install to a specific device (which requires the 7-tap developer mode on the device mentioned by others)
My case, hope it help. (Internal testing)
Make sure:
Change your version code for new release.
Add tester emails.
After upload and share link, must do these steps to download:
Open the Google Play Store app Google Play.
Click the Menu icon Menu > Settings.
In the "About" section, tap the Play Store version 7 times.
Once the Internal App Sharing setting appears, tap the switch to enable internal app sharing.
Click Enable.
Hours on this.
In my case the missing step was to enable Managed Google Play, which "Manage your private app and make it available to specific organisations". You don't need to apply an organisation filter, and simply use the internal test tracks.
The setting is found in Setup > Advanced Settings > Managed Google Play
#pierre was right. But that was some time ago, and now that link is not called Opt-in URL, but Join on the web. Just ask your testers to open it before they download the application.
We just had a related issue in this completely horrible process - documenting here because it burned a week for us.
Problem: We got approved on closed and production 2x but no one could see our app in internal, closed, public test tracks or on the public store.
How it happens: As far as I can tell when you start a Closed Test Track an organization gets auto-selected on Setup > Advanced Settings > Managed By Google and/or you can (irreparably!) set one yourself on the Closed Testing page. This means that only people in your org will be able to access it.
Solution: If Internal/Closed/Production is not showing up the solution may be: In Setup > Advanced Settings > Managed By Google you UN-check your org for it to be publicly available, as in the helpful alert in the screenshot below.
Duh. Worst default ever? :)
For me, i clicked the link play console gave me on phone
https://play.google.com/apps/internaltest/***********
But it didn't work, i clicked the link with pc, got the play store link, and clicked link on phone, and it worked !
For me, the issue was that of the version X.Y.Z, Google Play Console uses Z to determine the newest version of the app. So if, for example, the previous version of your app was 1.70.170, then 2.1.171 would work, but 2.1.1 would not show up for you as it would be considered older than 1.70.170.
Once you got the application from google play store link will be available on internal testing page inside.
Click on Internal testing
Step 1: Click copy link and use any browser
Step 2: after that it will show Accept Invitation already you are opened your added mail id from the google play developer console for internal tester on this application.
Step 3:
finally click on download it on google play
thats all. enjoy your coding...
Go to settings --> then internal app testing and add your testers there. Follow the instructions in this video https://www.youtube.com/watch?v=gAiu76l4-7s
I have a dev version of my app that is not published in the Play Store. I would like to test dynamic links with it, but whenever I click a dynamic link, it opens the play store, and I get a not found error (because there is no corresponding package in the Play Store).
What's the recommended way of testing this? It would also apply to staging environments, etc... that are not published.
I was able to test it like this:
I published a closed alpha version of an app - open only to my email (beta should work just the same)
Opted in via the opt-in link in the developer console (it's on the APK section)
After that, clicking the dynamic link I created on the Firebase console worked as expected, without having my app out in the open.
Caveats:
Connected Google users - might cause a problem if only one is on the alpha group list
It takes a bit of time to get started. Make sure you can see the app in Google Play before trying to click the link
Updates, fixes and changes take time until they actually appear on Google Play. Google Play now offers internal testing, a level below alpha that propagates updates quicker.
The other answer above is technically correct, but you can get close to simulating the real behavior without putting anything on the Google Play Store.
If your application is installed, the dynamic link will open your application. This is true even if your app is not listed on the Play Store. If this is not working for you, your app is not properly set up to receive dynamic links.
If your application is not installed, you will be taken to the Play Store and you will see app not found. After, you can sideload the app to simulate a Play Store install.
I have recently set up basic In App Purchases in my Android app that I am building. The problem I am having is that every time I install the app, via USB, I get the error "This version of the application is not configured for billing through Google Play. Check the help centre for more information.".
It seems that the only way I can do a real test, using real SKUs is by uploading to the beta test group and installing from there. This can take up to 2 hours.
I am aware that I can use the SKU "android.test.purchased" instead of my own SKUs which I have created with the Android dev console. This is not ideal as it slows down my development time.
I am sure I am missing something and I was hoping someone could please point me in the right direction.
Thank you Karen.
Worked out my issue was due to not signing my app with the keystore each and every time I build the application and installed via USB.
This option can be found in File -> Project Structure
Then select the module that you are signing, and then the tab "Signing" from the top of the window.
From there you just need to press the plus and fill in your details for the keystore.
After which, you need to go to the "Flavors" and "Build Types" tabs and select the signing config (one you just created).
My application is currently in alpha. On the google play developer console, I accidentally uploaded a new APK as production rather than alpha.
In advanced mode, there is a deactivate button. But if I deactivate and try to save I get the generic message "The application could not be saved. Please check the form for errors." I don't see any errors on the form. How do I deactivate?
I tried uploading a later version to alpha - that seems to work - but I don't want ANY version in Prod, as my app is not yet ready for prime time.
According to a Google customer service rep I contacted:
The Deactivate button is provided in your advanced mode when you want to support multiple APKs but when your new update supports the same number of devices as your previous APKs, the system won't allow such update. So it is required for you to deactivate the older version in order to upload your new APK.
The Deactivate button is only useful for situations where you have multiple active APKs.
Furthermore, discussing with them, there is apparently no functionality at this time that allows for you to remove APKs from the Production tab once they've been uploaded to that tab, AND there's apparently no way to enable Beta testing if your app is unpublished, so at this point it seems there's no way to undo what you've done if you accidentally upload an APK to the Production tab by mistake. The workaround proposed by the representative was to change the package name of the app, change the keystore used to sign, and create an entirely new application.
Further discussion with the representative indicated that the "error" is that you can't have a Production tab without an APK if there was one there already, but it sounds like there's a bug in that it doesn't actually report that that's the cause.
In latest play console you can goto Publishing Overview->managed publishing status-> press manage button on right then turn on managed publishing