How to Reapply After Google Play Requires More Testing

When a production-access application says that more testing is required, improve the test before sending the same answers again.

The key question for a reapplication is: What did you add, change, and verify after the previous application?

Step 1: Organize the previous test record

Create a summary of:

• The date the test first reached at least 12 participants
• The number of testers who remained enrolled
• Anyone who left the test
• Features that were checked
• Devices and Android versions covered
• Feedback received
• Published versionCode values
• Changes made
• Answers submitted in the previous application

When the original records are incomplete, begin a proper tracking table for the additional test.

Step 2: Recheck tester count and duration

Before starting additional scenarios, confirm that at least 12 testers are still participating.

• Was the person only added to an email list?
• Are they using the correct Google account?
• Did they complete opt-in?
• Did anyone leave the test?
• Did anyone move to another track?

Maintain more than the exact minimum when possible so that one departure does not break the qualifying state.

Step 3: Add scenarios that differ from the previous test

Repeating the same actions makes it difficult to explain the value of additional testing.

Examples of new scenarios include:

• Time required from first launch to completed registration
• Recovery after a network error
• Behavior when a permission is denied
• Small screens and large text settings
• Data retention after an app update
• Long-lived sign-in sessions
• Saving multiple images or data records
• Clarity of error messages

Step 4: Give testers specific instructions

Please check the following during this additional test:
1. Guidance shown after a failed sign-in
2. The completion state after saving data
3. Whether saved data appears after restarting the app
4. Layout with a larger system text size
If you find a problem, send the device model, Android version, and steps that caused it.

Step 5: Prioritize the feedback

You do not need to implement every request. Record why an item was postponed or declined.

Step 6: Publish the revised build

When changes are made, increase the versionCode and publish a new AAB to the same closed-testing track.

Example release notes:

Additional test build
- Improved sign-in error guidance
- Added a save-completion message
- Fixed layout issues with large text sizes

Confirm that testers can receive the latest version.

Step 7: Record the retest result

F-003 Save completion state
Report: It was unclear whether saving had finished
Change: Added a completion message and changed the button state
Released build: versionCode 45
Retest: Passed on Pixel 8 and Galaxy S23

Do not record only that the issue was fixed. Keep who verified it, which build was used, and the result.

Step 8: Rewrite the reapplication answers

Example answer

After the previous application, we continued the closed test with additional scenarios.
Testers checked sign-in failure guidance, the display after saving data, and data retention after an app update.
They reported that the save-completion state was unclear and that part of the layout broke with a large system text size.
We added a completion message, adjusted the layout, published the revised build to the same test track, and verified the affected flows again on multiple devices.

Replace the example with the actions that actually occurred in your test.

Make the difference from the previous application explicit

Prepare a comparison table before writing the final response.

Use only figures supported by your records.

Reapplication approaches to avoid

• Resubmitting the same text immediately after the notice
• Repeatedly replacing the testers
• Asking people only to join without using the app
• Claiming fixes that were not implemented
• Demanding guaranteed approval
• Saying that an outside service guarantees production access

Checklist before reapplying

• Confirmed the current tester count
• Defined additional test scenarios
• Testers actually used the app
• Recorded the feedback
• Fixed important issues
• Retested the revised build
• Can explain what changed since the previous application
• Answers match the actual app and test

Summary

A reapplication is not simply another waiting period.

Identify the weakness
→ Run additional tests
→ Collect feedback
→ Make changes
→ Retest
→ Rewrite the answers

When rebuilding the application response, also see How to Answer the Google Play Production-Access Application.