Android Question ProGuard

[sadegh nordeh]

Hello everyone
The problem in Basic is that we cannot set ProGuard and when the application is sent to Google, we get a crash problem, but in the Apk version we do not have any crashes even when we use obfuscated, but when the bundle version is sent to Google, these problems are due to the lack of an environment to import

# Add project specific ProGuard rules here.
# You can control the set of applied configuration files using the
# proguardFiles setting in build.gradle.
#
# For more details, see
# http://developer.android.com/guide/developing/tools/proguard.html

# If your project uses WebView with JS, uncomment the following
# and specify the fully qualified class name to the JavaScript interface
# class:
#-keepclassmembers class fqcn.of.javascript.interface.for.webview {
# public *;
#}

# Uncomment this to preserve the line number information for
# debugging stack traces.
#-keepattributes SourceFile,LineNumberTable

# If you keep the line number information, uncomment this to
# hide the original source file name.
#-renamesourcefileattribute SourceFile

There is
Please Erel to provide a place to enter the ProGuard settings in the next update.
Thanks to the BASIC development team
@Erel

 

[Dave O]

Is this related to the ObfuscatorMap.txt file?

I'm still hoping that B4A adds support for generating the file format that the Google Play console wants. It's tedious to look at stack traces on their console and have to manually translate "vvvvvvvvvvvvvvv0" to a readable sub name using the .txt file.

 

[Sandman]

Probably relevant Wish from 2022:

Add support for mapping.txt to simplify debugging via Google Play Console

It would be nice if the compilation would make an additional file "mapping.txt", containing the data mentioned by Google during APK upload: I fully realize we can do this ourselves using the existing ObfuscatorMap.txt, but life is short and this would probably save quite a few people time...

www.b4x.com