If you are an Android developer looking to publish an app, you already know about the strict 14-day closed testing requirement. But merely having 20 testers install your app isn't enough—you need to know if the app is actually stable when they use it.
Relying solely on testers to manually report bugs is a mistake. Users often don't know how to articulate what caused a crash, or they might just ignore it entirely. This is why integrating Firebase Crashlytics during your closed testing phase is absolutely critical.
In this guide, we'll explain how to set up Firebase Crashlytics to specifically monitor your Google Play testing tracks so you can fix critical bugs before applying for production access.
1. Link Firebase to Your Google Play Console
The most powerful feature of Firebase Crashlytics for Android developers is its deep integration with the Google Play Console. When linked, Crashlytics can automatically recognize your Google Play testing tracks.
How to link them:
- Go to the Firebase Console and select your project.
- Navigate to Project settings > Integrations.
- Find the Google Play card and click Link.
- Follow the prompts to authorize Firebase to access your Google Play developer account.
Once linked, Firebase will automatically sync data regarding your app releases across the Internal, Closed, Open, and Production tracks.
2. Filter Crash Reports by Testing Track
During the 14-day testing period, you will likely be pushing multiple updates to the "Closed testing" track. You need to separate these crashes from your internal debug builds.
According to the official Firebase documentation, once your accounts are linked, you can filter crashes by Play track directly in the Crashlytics dashboard:
- Open the Crashlytics dashboard in Firebase.
- Click on the Filter menu near the top of the page.
- Select the Google Play track (e.g., "Closed testing").
This allows you to focus exclusively on the crashes experienced by your 20 testers, rather than noise generated by your own local development.
3. Log Custom Keys and User IDs
A stack trace is helpful, but context is king. Why did the app crash on that specific screen?
To get the most out of your closed testers, configure Crashlytics to send custom keys and state information leading up to the crash.
- Custom Keys: Log state variables (e.g.,
Crashlytics.getInstance().setCustomKey("current_level", 4)). - User IDs: If your app requires login, log a hashed version of the user ID. If one specific tester is experiencing a crash loop, you can reach out to them for more details.
[!WARNING] Never log personally identifiable information (PII) like raw email addresses or phone numbers to Crashlytics, as this violates privacy policies and could lead to your app being suspended.
4. Don't Confuse Crashlytics with App Distribution
A common mistake developers make is including the full Firebase App Distribution SDK in the build they upload to the Google Play Console.
Google explicitly advises against this. The App Distribution SDK is meant for distributing pre-release builds outside of Google Play. If you include the full SDK in a build submitted to a Google Play closed or open track, it can cause policy violations or unexpected behavior. Use standard Crashlytics for monitoring Play Console tracks.
5. Pair Crashlytics with Professional Testers
Crashlytics is an amazing tool, but it only works if people actually open and interact with your app. If you've asked friends or family to be your testers, they might open the app once on day one and never look at it again.
This results in a completely empty Crashlytics dashboard—not because your app is bug-free, but because it's not being tested. Check out our article on why family members make terrible testers to understand this trap.
To ensure your app is rigorously tested, you need real users pushing it to its limits. This is where 12-App Tester comes in.
We provide a dedicated team of 20+ professional Android testers who will actively use your app for 14 continuous days. Combined with Firebase Crashlytics, our testers will help you uncover hidden memory leaks, ANRs (Application Not Responding errors), and edge-case crashes.
By fixing the issues our testers uncover in Crashlytics, you can vastly improve your app's Android Vitals. Learn more about how ANRs and crashes destroy your app ranking and start your QA campaign with 12-App Tester today!