-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while encoding APK file with apk-mitm and Apktool #158
Comments
However, it is not possible to set these apktool settings in mitm-app? I couldn't find it. Please help me
|
Solution to the problem: during --wait function you should copy the files to another location, add resources.arsc to the decoded folder and enter the path to the decoded folder in place of the former path to the application. However, I got another problem: signing the app doesn't work. Lol. Stupidity |
It's all about Apktool compatibility. I think only apktool dev can bring any changes to make it works. Check that: iBotPeaches/Apktool#3436 |
Hello,
I ran into a problem when trying to use apk-mitm to decode and modify the APK file. There appears to be a bug with Apktool and AAPT during the encoding process. On default version of Apktool it stops on error while Decoding APK file
Here are the details:
apk-mitm version: 1.2.1
Apktool version: 2.9.3
APK file: com.facebook.orca_452.0.0.50.109-320409634_minAPI21(armeabi-v7a)(360,400,420,480dpi)_apkmirror.com.apk same error with different versions and different tested apk e.g. youtube
Operating system: Windows 11
Path to apktool.jar: C:\Windows\apktool.jar it's 2.9.3 but I have tried also with few oldest
During the encoding process, I receive many errors regarding invalid XML file paths in the
res\color.2\
directory. Here is my console:I can also provide full logs if required. Could anyone help me understand what might be causing these errors and how to fix them?
Thank you for your help.
The text was updated successfully, but these errors were encountered: