Deobfuscation to expose stack trace

Hi folks,

We’re seeing an issue reported in the Play Store with our app published via Expo 27:

java.lang.SecurityException:

at io.nlopez.smartlocation.location.a.a.a (LocationGooglePlayServicesProvider.java:158)
at io.nlopez.smartlocation.location.a.a.onConnected (LocationGooglePlayServicesProvider.java:221)

Which initially seems similar to that reported here:
https://github.com/mrmans0n/smart-location-lib/issues/229

However, the obfuscated stack trace prevents us from determining this for sure.

The Play Store would really like me to “upload [my] ProGuard deobfuscation file in order to deobfuscate future stack traces”, and I’d like to do that too.

How can I access the mapping.txt that was produced during the build of my project?

Thanks!
G

Hi @thetanz-geoffrgwilli - thanks for the question. Currently the only way to get access to this file is to detach and build the apk yourself. You can also add a feature request for this if you want it to be available for normal standalone apps.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.