apktool d -f -r --force-manifest app.apk -o appand then again recompiled using
apktool b -a $(which aapt) app -o app2.apkand finally I unzipped the recompiled app
unzip app2.apkand I found that
AndroidManifest.xmlwas not recompiled means it is still in text format
Hey, so I want to add frida (need to circumvent ssl pinning in an app, following this https://koz.io/using-frida-on-android-without-root/ )
But when I've decompiled the app I can't find a lib subfolder so what I tried was to mkdir lib/ and put the frida .so in there, but when I've recompiled the app crashes I assume I don't add the .so correctly)
Worth to note is that I use the -r -f flags because otherwise I can't rebuild it
I've got no idea how to even start debugging this, I tried to use adb logcat and grep for the apk but it doesn't mention what kind of error happens.
Hi there, I'm looking a bit deeper in Apktool to understand better how resources are handled during build.
I found the ROADMAP.md file which seems to give a bit more detail on intentions.
My question is straightforward: is it possible to add a given resource to a decoded apk, reference it into smali code and then recompile it ?
Hey Guys, i tried to decompile and compile an app with apktool and i get lots of errors like
AndroidManifest.xml:43: error: No resource identifier found for attribute 'requestLegacyExternalStorage' in package 'android'
i tried the latest jar file of apk tool. Is there any plan when the apk tool is working?