Google Play Console内部测试链接无法使用问题咨询

Based on your situation—submitting your app twice (first .AAB, then .APK) to Internal Testing, testers facing broken download links, and unclear status in the Play Console—let’s break down the root causes and actionable steps to fix this:

What’s Going On? #

• You submitted your app on Nov 6, and as of Nov 9, the internal testing links aren’t working for testers (either infinite load or "URL not found" errors).
• The main culprit here is likely ongoing or restarted review processes, compounded by Google’s extended review windows for some developer accounts.

Google’s Official Guidance (Direct Quote) #

We understand your concern about your app's pending status. Note that after submitting a new app or update to Play Console, processing time is required to complete the Google Play publishing flow. If you modify the app while it's under review, the review cycle will restart, and submissions cannot be withdrawn or canceled. We recommend planning carefully to avoid repeated submissions.

For some developer accounts, we extend review times to better protect users, with review durations up to 7 days, and potentially longer in special cases. You can check the current status on the Publishing overview page. Once review is complete, the "Changes in review" section will show "You don't have any changes in review." Additionally, if managed publishing is enabled, you must click "Review and publish" for the update to be released.

Actionable Fixes to Try #

• Wait it out (up to 7 days): Your submission is only 3 days old, and Google explicitly states reviews can take up to 7 days (sometimes longer) for certain accounts. The download link won’t activate until the review finishes and the build is pushed to the internal testing track.
• Check the Publishing overview page: Ignore the unclear dashboard status—this is the official place Google directs you to for real-time review updates. Keep an eye out for the "Changes in review" section to show no pending changes, which means review is complete.
• Double-check managed publishing: If you have this setting turned on, the build won’t go live automatically after review. You’ll need to manually navigate to the Console and click Review and publish to make the build available to testers.
• Avoid future submission restarts: Switching from .AAB to .APK for your second submission likely reset the review clock. Stick with one build format for your current test cycle to prevent unnecessary delays.

内容的提问来源于stack exchange，提问作者Aleksandar Zoric