Consider the following key points and best practices before you publish an application to Google Play.
To help launch an Android application successfully, Android provides best practices to follow. You can find these best practices in Android’s Launch checklist documentation.
If your application crashes on a device, Google can use an Android symbols package to make a native stack trace human-readable on the Android Vitals dashboard. It’s best practice to generate a Public symbols package for your application and upload it to Google Play. For information on how to do this, refer to Generating a symbols package.
Similar to symbol files, Unity can produce a deobfuscation file if you apply minification to your application build. For more information on applying minification, refer to Android Player Settings. A deobfuscation file is automatically generated as a mapping file in the same location as your application build.
If you apply minification, it’s best practice to upload the deobfuscation file when publishing your application on Google Play. A deobfuscation file deciphers the method names in the stack trace, allowing you to identify and resolve the exact cause of the application crashes. For more information, refer to Google’s documentation on Deobfuscate or symbolicate crash stack traces