ChatGPT解决这个技术问题 Extra ChatGPT

Google App is Published on Internal Test Track but Can't Be Found/Downloaded

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...

https://i.stack.imgur.com/7BEoz.png

https://i.stack.imgur.com/mmg3Y.png

https://i.stack.imgur.com/yTzwv.png

...but it results in the same message stating the App can't be found.

https://i.stack.imgur.com/PagDq.png

https://i.stack.imgur.com/0r7QE.png

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.

Google Play Console > Release > Internal App Sharing > Select "Anyone you shared the link with can download" - even though I was already on the list, this is what made it work ¯\_(ツ)_/¯

P
Pierre

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.

https://i.stack.imgur.com/LCITu.png


Ah so it takes time for this link to show up! I swear there is no mention of that on the portal, it seems like an instant thing, no wonder I was confused/thought I had made a mistake!
The internal test track is only available to apps already published in the store.
what on earth. the 'only applies to already published app' is such a crucial piece of info that needs to be made more obvious!
If the internal test option is only available to already published apps why google is letting me use the internal test option! This is crucial! I was looking into this for over two hours! Google a multi billion company cant use child logic to help developers do their job. Unbelievable situation!
Is that true? You can only internally test an already published app? That makes little (well, no) sense?
b
babie

Please delete cache and data of google play app on your device, then new updated version will be available


For those of us not used to having to manage the cache of installed applications manually: This varies by device/OS version but some combinations of: Apps → Settings → Device (if displayed) → Apps/Applications/App Manager/Application Manager → Shows list of all apps installed → Google Play Store → Storage (if displayed) → Clear Cache/Clear Data (or search Google for your specific device)
I have to do this every time I use a new internal test version of another package name. Seriously..
If you have followed the steps in the accepted answer, this is most likely what will solve it for you
Since the acceptance answer has a million comments, I'll add one here to give weight to this answer: @barbie's suggestion worked for me to get rid of spinner (even if it was to get "not found" instead — that's better than interminable blank screen spinner). I still can't believe manual data & cache delete is needed though.
G
Gayan Weerakutti

For Android App Bundles (AAB)

https://i.stack.imgur.com/wYtFM.png

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.


I'm getting the error: "The app '' needs to be published before you can use internal app sharing." :( Kinda defeats the whole point for it
@DShook Maybe your package name is invalid. stackoverflow.com/a/57594516/3647002
This works great, thanks so much. One note to people who have multiple Google Accounts. Make sure on Google Play Store you are logged into to the one that you selected when uploading the bundle/APK. If you dont you will get an infinite loading spinner.
I found that the user also has to uninstall the publicly available version of your app from their phone before it allows install from the shareable link. Also needed to set permission according to stackoverflow.com/a/63205627/536625
Thank you so much for the detailed response!!!!
b
blalond

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

https://i.stack.imgur.com/S5wv3.png


THIS was it! The old console was bad. The new console is worse. So unclear. Note: I also had to make the app NOT DEBUGGABLE.
Thanks so much, this was the solution. They could not have designed it worse.
This worked for me. The "internal app sharing" link didn't work until I set these permissions. Create such a link via this answer: stackoverflow.com/a/63205627/536625
S
Sean K

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)


A MONTH!! Wow. I would say this is an edge case as the longest review time i've personally ever experienced is ~24 hours and typically less.
The review process is not required for Internal testing tracks. You just upload it, without descriptions, screenshots, nor answering the 700 questions for public apps, and it's ready to be installed on any device/emulator. Also, make sure to add the users to the Testers list, otherwise the store won't show the app (even with the invite link - it is for inviting members of your list exclusively).
N
Nigel

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

https://i.stack.imgur.com/6Sx1f.png


I think your solution is about closed testing tracks and question is about internal testing tracks. Closed != Internal and your anwser that you can simply use "internal test tracks" is a bit confusing when compared to what is available in those Managed Google Play settings. Even on the screenshot you can see it says "closed testing tracks". Or the case is that closed tracks settings influence internal settings, that wouldn't be a total surprise ;-)
Careful with this - we just went to production and no one could see it due to this Managed By Google Play setting (which we definitely didn't select). In Setup > Advanced Settings > Managed By Google play you need to UNcheck your org for it to be publicly available!
Now remove option is removed too! WARNING WE NEED TO CREATE A NEW APP IF WE ACCIDENTALLY ENABLE MANAGED GOOGLE PLAY - YUK!
That sounds concerning. However, I just checked our app which is has "Managed" turned on, and we can still turn it off. I'm interested to see if other people have lost the ability to disable it too?
No, be careful. Don't turn it on. This is totally a different thing. And If you enabled it you won't be able to revert that.
T
Thang Tran

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.

https://i.stack.imgur.com/7LXLI.png


p
politebarista

https://i.stack.imgur.com/SkqFS.png


N
Niko Dunk

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.

https://i.stack.imgur.com/x1fM3.png

Duh. Worst default ever? :)


T
Taylor Kline

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.


Version name does not manage order at console, that would be version code. developer.android.com/studio/publish/versioning#appversioning
@VictorR.Oliveira correct, we use the Z as our versionCode.
n
nesibeyyubov

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 !


C
Chefk5

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