By default, all the code protected by Android App Protection is placed in a randomly named package, which may pose problems if integration relies on knowing the package name.
To address this issue, the 'packageNamePrefix' blueprint parameter can be used. However, this option only adds additional package to the existing one. Therefore, the final package is no longer 'abc' (set in blueprint), but 'abc.<RANDOMLY_GENERATED_FOLDER>.
So now, if you for example try to refer to signature of dedicated method from code, you can't change seed without changing code, because it will automatically change the method's signature.
In Java ByteCode Protection, this option worked in a different way. It put all protected classes directly in package, whose name matched the packageNamePrefix from blueprint. We would like to see a similar opportunity in Android App Protection.
by: Kamil P. | about a month ago | Cloud Management
Comments
Thank you for submitting this idea. We will take this into consideration as we build our roadmap and follow up as necessary.