search

ClaudiuGeorgiu / Obfuscapk

An automatic obfuscation tool for Android apps that works in a black-box fashion, supports advanced obfuscation features and has a modular architecture easily extensible with new techniques
MIT License
1.08k stars 284 forks source link

Whether About is Bundle Support aab? #157

Closed TheRangerStar closed 8 months ago

TheRangerStar commented 1 year ago

Do the project currently support aab operation? 👀👀👀

ClaudiuGeorgiu commented 1 year ago

Hi, there is some support for bundles (see https://github.com/ClaudiuGeorgiu/Obfuscapk/pull/121), but is not tested as much as with apk files (I always used Obfuscapk only on apk files).

TheRangerStar commented 1 year ago

Hi, there is some support for bundles (see #121), but is not tested as much as with apk files (I always used Obfuscapk only on apk files).

Dear @ClaudiuGeorgiu : Thank u for your reply ,,,I looked at the document again and found the introduction of aab. Then I follow the instructions in the document. But until I cd toObfuscapk/src on the terminal,Then the following questions were reported: image How can I solve it,Looking forward to your reply

TheRangerStar commented 1 year ago

Hi, there is some support for bundles (see #121), but is not tested as much as with apk files (I always used Obfuscapk only on apk files).

Dear @ClaudiuGeorgiu : Thank u for your reply ,,,I looked at the document again and found the introduction of aab. Then I follow the instructions in the document. But until I cd toObfuscapk/src on the terminal,Then the following questions were reported: image How can I solve it,Looking forward to your reply This is my environment variable image

ClaudiuGeorgiu commented 1 year ago

Hi @TheRangerStar, if you're using APKTOOL_PATH, BUNDLE_DECOMPILER_PATH, APKSIGNER_PATHand ZIPALIGN_PATH you have to provide the path to the executable, not the directory containing it. It's a bit different from the classic PATH variable where you only specify the directory, sorry for the confusion. So in your case you should set BUNDLE_DECOMPILER_PATH=/Users/a001/bin/BundleDecompiler.jar (if that's the name you gave to the jar file). The same applies to the other variables above: specify the full path of the executable and not the directory containing it.

TheRangerStar commented 1 year ago

Hi @TheRangerStar, if you're using APKTOOL_PATH, BUNDLE_DECOMPILER_PATH, APKSIGNER_PATHand ZIPALIGN_PATH you have to provide the path to the executable, not the directory containing it. It's a bit different from the classic PATH variable where you only specify the directory, sorry for the confusion. So in your case you should set BUNDLE_DECOMPILER_PATH=/Users/a001/bin/BundleDecompiler.jar (if that's the name you gave to the jar file). The same applies to the other variables above: specify the full path of the executable and not the directory containing it.

Ok, I will try it later. Thank you for your reply