BrutException: could not exec about apk-mitm HOT 2 CLOSED

First of all - Thank you for this amazing tool! It works flawlessly on two apps I already tried.

Thanks! 😄

Would you be able to help here / point me into the right direction (looking into issues in the apk tool library you built this tool on) ?

In case any of these errors are actually the result of a bug, then it would definitely be in Apktool as the only things apk-mitm is concerned with are files that have to do with certificate pinning in some way. But this might also be the fault of the app developer since there's not much Apktool can do when an APK contains files that are invalid in some way.

Regarding your logs: 99% of the problems you run into with Apktool result in a brut.common.BrutException, so you can basically ignore that part, it doesn't hold any meaning. Instead, look at the W: lines before that. You might think they're just warnings, but they often contain the reason a command failed.

From your logs, these are the most relevant lines:

W: ...\decode\res\drawable-nodpi\placeholder.png: error: failed to read PNG signature: file does not start with PNG signature.
W: ...\decode\res\drawable-nodpi\placeholder.png: error: file failed to compile.

W: libpng error: Not a PNG file
W: ERROR: Failure processing PNG image C:\Users\\AppData\Local\Temp\apk-mitm-e0aca39ecedcc4a02dfbff425e785cac\decode\res\drawable-nodpi\placeholder.png
W: ...\decode\res\values\styles.xml:318: error: Resource entry AppTheme already has bag item colorPrimary.
W: ...\decode\res\values\styles.xml:317: Originally defined here.

W: Cant find 9patch chunk in file: "drawable-xhdpi-v4/com_facebook_tooltip_blue_background.9.png". Renaming it to *.png.
W: Cant find 9patch chunk in file: "drawable-mdpi-v4/common_google_signin_btn_icon_dark_normal_background.9.png". Renaming it to *.png.
W: Cant find 9patch chunk in file: "drawable-mdpi-v4/common_google_signin_btn_icon_light_normal_background.9.png". Renaming it to *.png.
...

You can try searching Apktool's issues for these messages, maybe you'll find a way to fix these errors. Note that you can always make manual changes to an APK (preferably with APKLab) get it to re-encode successfully.

from apk-mitm.

Closing this because none of the errors seem to be caused by apk-mitm itself.

from apk-mitm.