You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, APKLab heavily relies on Apktool for decoding and rebuilding. However, many modern APKs (especially those with complex resources or unconventional obfuscation) often encounter errors during the rebuild stage when using aapt or aapt2 via Apktool. Some related issues: #224
Describe the solution you'd like
I suggest integrating APKEditor as an optional/alternative engine for the "Decode/Build" process.
Why APKEditor?
AAPT/AAPT2 Independence: APKEditor's implementation is independent of aapt/aapt2. It handles resources in a way that bypasses many common Apktool rebuild errors.
Robustness: For many APKs that fail to rebuild after being processed by Apktool, APKEditor often works seamlessly without resource corruption.
Describe alternatives you've considered
Currently, I have to manually use APKEditor's CLI to decompile APKs and then import them back into APKLab, then use CLI again to recompile them, which breaks the seamless integrated experience.
Additional context
Integration could be implemented as a toggle in the settings or a choice during the initial APK analysis stage (e.g., "Choose engine: Apktool / APKEditor").
Is your feature request related to a problem? Please describe.
Currently, APKLab heavily relies on Apktool for decoding and rebuilding. However, many modern APKs (especially those with complex resources or unconventional obfuscation) often encounter errors during the rebuild stage when using aapt or aapt2 via Apktool. Some related issues: #224
Describe the solution you'd like
I suggest integrating APKEditor as an optional/alternative engine for the "Decode/Build" process.
Why APKEditor?
AAPT/AAPT2 Independence: APKEditor's implementation is independent of aapt/aapt2. It handles resources in a way that bypasses many common Apktool rebuild errors.
Merge APK Support: A key advantage of APKEditor is its ability to merge Split APKs (App Bundles) into a single, standalone APK. This would significantly simplify the workflow in APKLab when dealing with multi-APK installations. This may solve issue Merges multiple splitted apk files to standalone apk #223, Support bundle apk (apks & xapk) #39
Robustness: For many APKs that fail to rebuild after being processed by Apktool, APKEditor often works seamlessly without resource corruption.
Describe alternatives you've considered
Currently, I have to manually use APKEditor's CLI to decompile APKs and then import them back into APKLab, then use CLI again to recompile them, which breaks the seamless integrated experience.
Additional context
Integration could be implemented as a toggle in the settings or a choice during the initial APK analysis stage (e.g., "Choose engine: Apktool / APKEditor").