Sandman Expert Licensed User Longtime User Apr 12, 2022 #1 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 during their bugfixing. (I did find some information on the format of the mapping.txt in this post: what is the number part in mapping.txt A generated mapping.txt like following com.abc.media.MediaAudioEncoder$AudioThread -> nq: com.abc.media.MediaAudioEncoder this$0 -> a 100:100:void <init>(com.abc.media.MediaAudioEncode... stackoverflow.com Not as simple as ObfuscatorMap.txt, but it doesn't seem overly complicated either. I was researching if it would be possible to create a B4J tool to convert ObfuscatorMap.txt to mapping.txt, but looking at the format I can't see a way to do it. It's probably something that needs to be done during compilation, as far as I can tell.)
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 during their bugfixing. (I did find some information on the format of the mapping.txt in this post: what is the number part in mapping.txt A generated mapping.txt like following com.abc.media.MediaAudioEncoder$AudioThread -> nq: com.abc.media.MediaAudioEncoder this$0 -> a 100:100:void <init>(com.abc.media.MediaAudioEncode... stackoverflow.com Not as simple as ObfuscatorMap.txt, but it doesn't seem overly complicated either. I was researching if it would be possible to create a B4J tool to convert ObfuscatorMap.txt to mapping.txt, but looking at the format I can't see a way to do it. It's probably something that needs to be done during compilation, as far as I can tell.)