I have an Android app written in Oxygene and published on the Google Play Store. My app crash report Stack Traces in the Google Play Console seem to indicate that the code has been obfuscated.
The stack traces look like this, for example:
java.lang.NullPointerException: at MyFileName.SomeObject.MethodName (Unknown Source: 56) at MyFileName.AnotherObject.NewMethodName (Unknown Source: 27)
Instead of this:
java.lang.NullPointerException: at MyFileName.SomeObject.MethodName (MyFileName: 9231) at MyFileName.AnotherObject.NewMethodName (MyFileName: 3672)
In a typical Android project run via Android Studio and the standard toolchain, this is caused by ProGuard and can be fixed with the correct ProGuard settings or by uploading the
mapping.txt file to the Play Console to deobfuscate (all described here).
Is EBuild obfuscating code in the build process? If so, is there a
mapping.txt produced similarly to ProGuard?