Anyway: remember that this tools aren’t enabled by default and you need to take are about it. □ It can introduce security issues: what if someone decompiles the generated artifact and found that you are doing some tricks to avoid a validation? What if someone manages to replicate that behavior? Edit: If you are using Proguard/R8 this isn’t a real problem for you, because the compiler optimizations will hide the real condition. ![]() I agree that we shouldn’t ship debug functionality in the published artifact, and there are many reasons for that: I would not want to ship Debug functionality in our Production APK/Bundle code. ![]() The problemĮverything seemed fine to me until I received a comment in the pull request: ![]() I relied on the BuildConfig.DEBUGconstant generated by Android Studio.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |