Internal testing

Internal testing is the fastest Play track. Builds are available to up to 100 testers within minutes of upload, with no Play review. It needs almost nothing set up: as long as your app exists in Play Console and a valid AAB uploads, testers can install it. The store listing, content rating, and App content declarations are only needed for production.

#Trigger your first build

1. From the rubynative.com dashboard, open the app and click the Android build button.
2. Preflight runs in about five seconds. If it fails, fix the underlying issue (usually a missing service account invite, or the app not yet created in Play Console) and retry.
3. The Gradle build runs (2 to 7 minutes) and produces an AAB.
4. The AAB uploads to the Internal Testing track on Play Console automatically.

If the AAB build succeeds but the Play upload fails, the build is marked success (the AAB is downloadable from the dashboard) and a separate Play-specific error message is attached. Fix the issue it names and re-trigger the build.

#Add testers

If you've filled the Beta testers field in Ruby Native, the same Play Console panel in the dashboard has a copy-button list of emails.

Once the first AAB lands on the Internal Testing track:

1. In Play Console, go to Testing -> Internal testing.
2. Click the Testers tab.
3. Click Create email list and paste in tester emails, or share the Copy link opt-in URL.
4. Testers install the app from the link on their Android device.

Testers must accept the opt-in URL once before they can install the app. The URL stays the same across builds, so you only need to share it once.

Google's set up an open, closed, or internal test guide has the full walkthrough.

#Troubleshooting

The preflight and upload steps emit specific error messages. Each maps to a setup step:

If you imported an existing AAB or signing key and Play prompts you to accept App Signing, click through once in Play Console, then retry the build.