The app crashes at start for several testers

A blocking bug in the tested release stops testers on day 1. Fix it, publish a new release with a higher version code and announce it to testers.

J
Written By JordanLast updated 1 hour ago

What you see

On day 1, several testers report that the app closes as soon as it opens, or that a blocking problem stops them.

Why

The tested release has a blocking bug, often on some phones or Android versions only, or because of a setting that only the release build has.

What to do

  1. Read the reports: each bug comes with the phone, the Android version, the steps and the screenshots.
  2. Look for the crash in Android vitals, in the Play Console.
  3. Fix it, raise the version code, upload the release to the closed testing track and send it for review.
  4. Once it's “Published”, open your test, fill “Announce an update” with the fix and click “Notify the testers”.
  5. If the app can't be used at all in the meantime, you can pause the test: Peerbeta counts no day and no window runs out until you resume it.

A crash found and fixed during the test is useful: Google's production access form asks what you changed after testing.

What Peerbeta does

When at least three testers report a crash or a blocking problem on day 1, the diagnosis sends you a priority alert.

Was this helpful?

Your feedback shapes what we write next.