About Proguard Mapping File upload to particular version while releasing apk in playstore

gistfile1.txt

PROGUARD
Generally ProGuard is a tool to help minify, obfuscate, and optimize your code.
It is not only especially useful for reducing the overall size of your Android application as well as removing unused classes and methods that contribute towards the intrinsic 64k method limit of Android applications. Because of the latter issue, ProGuard is often recommended to be used both in development and production especially for larger applications.
ProGuard can be enabled by using the minifyEnabled option for any build type. 
If you intend to use it for production, it is highly recommended you also enable it on your development.

https://miro.medium.com/max/2640/1*J-9cAvm8kSn001rXGDtwxg.png

Generally retracing this kind of error log have two ways.Lets discuss one by one
Get the mapping.txt file and retrace the logs using proguardgui
Obtain the mapping.txt file using the below path
app/build/outputs/mapping/FLAVOR/release/mapping.txt
Get the proguardgui using the below path as shown in the below screen shot


https://miro.medium.com/max/2640/1*rh5D6CmOQFUTSz2enFJhLg.png 

Proguard Retrace Window
Just load the mapping file and add the stack trace in obfuscated stack trace…….. and click on retrace window as shown in the below screen shot
Image for post
Cool you’ve just got the de-obfuscated stack trace locally…Congrats!……
2.Lets learn the second way
Take a look below:-
If you use ProGuard to optimize and obfuscate your APK files, you can upload a ProGuard mapping file for each version of your app on the Play Console to deobfuscate your crash stack traces and help you better analyze your app’s crashes.
Important: Only ProGuard mapping files are supported for deobfuscation.
Upload a ProGuard mapping file
To deobfuscate your app’s crashes for a version of your app, you need to upload the respective ProGuard mapping file for the same version of your app. To help you analyze your app’s crashes efficiently, it’s a good idea to upload a mapping file for each new version of your app.
Important: Once you’ve uploaded a mapping file for a version of your app, only future crashes for that version of your app will be deobfuscated. Crashes for a version of your app that happen before you’ve uploaded its respective mapping file won’t be deobfuscated.
To upload a ProGuard mapping file:
Sign in to your Play Console.
Select an app.
On the left menu, click Android vitals > Deobfuscation files.
Next to a version of your app, click Upload.
Upload the ProGuard mapping file for the version of your app.
Upload files using the Google Play Developer API
To upload files using the Google Play Developer API, go to the Google Developers site.
View deobfuscated crash stack traces
After you’ve uploaded a ProGuard mapping file for a version of your app, crashes that occur afterward will be deobfuscated. You can review deobfuscated stack traces for individual crashes on your app’s ANRs & Crashes page.
Sign in to your Play Console.
Select an app.
On the left menu, click Android vitals > ANRs & Crashes.
Select a crash.
On the “Stack Traces” tab, you’ll see your deobfuscated stack traces.

Read more about -> https://medium.com/@sagar.s.rao/d-obfuscating-google-play-store-crashes-logs-android-5b0a3c50da95
Note: Only unique stack traces for crashes are shown. If there are multiple identical crashes, they’ll only be shown once. The crash volume includes all instances of unique stack traces.