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
Have you tried apktool d, apktool b without changing anything? YES.
If you are trying to install a modified apk, did you resign it? YES.
Are you using the latest apktool version? YES.
I have attached two APKs that expose the same fault but referring to two different unexpected tags in the manifest. In both cases it is a clear fault of the app developer to include tags that shouldn't be there, but since you can install and run those APKs successfully, I was wondering whether aapt2 could simply ignore those tags during building? Just to be clear by dropping those tags from the manifest one can successfully rebuild them.
The text was updated successfully, but these errors were encountered:
Information
apktool -version
) - 2.9.0java --version
) - 15.0.2Steps to Reproduce
APK
https://github.com/tingsu/DroidDefects/raw/master/reproducible-cases/LibreNews-app.librenews.io.librenews-1.4-a/LibreNews-v1.4_debug.apk
https://github.com/tingsu/DroidDefects/raw/master/reproducible-cases/Passwordmaker-org.passwordmaker.android-1.1.11/org.passwordmaker.android_1.1.11.apk
Questions to ask before submission
apktool d
,apktool b
without changing anything? YES.I have attached two APKs that expose the same fault but referring to two different unexpected tags in the manifest. In both cases it is a clear fault of the app developer to include tags that shouldn't be there, but since you can install and run those APKs successfully, I was wondering whether aapt2 could simply ignore those tags during building? Just to be clear by dropping those tags from the manifest one can successfully rebuild them.
The text was updated successfully, but these errors were encountered: