-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[BUG] Decoding only manifest without remaining resources corrupts APK wrt signing #3389
Comments
I don't think a bug here. If you force manifest decoding (ie you don't decode How it actually built is the odd thing. I'll investigate that and either look towards a doc change or making this actually fail during compilation with a forced manifest. |
Here is the decoded AndroidManifest.xml code
|
This is so interesting to me that we built an obviously invalid Manifest and aapt2 was fine with it. My guess is all the protections we've ripped out over the years to lessen the strictness of the build has caught up to us. For example, once its built (without an error). Its clearly invalid.
Not sure what I want to do here yet.
|
Information
apktool -version
) - 2.9.0java --version
) - 15.0.2Steps to Reproduce
Frameworks
If this APK is from an OEM ROM (Samsung, HTC, LG). Please attach framework files
(
.apks
that live in/system/framework
or/system/priv-app
)APK
If this APK can be freely shared, please upload/attach a link to it.
https://github.com/iBotPeaches/Apktool/files/12774551/com.zola.bmi.apk.zip
Questions to ask before submission
apktool d
,apktool b
without changing anything? YESI am not even sure if this is a real bug since decoding only the manifest succeeded as above output showed? Btw, I did not try the suggested option by apksigner to overwrite the min sdk version manually.
The text was updated successfully, but these errors were encountered: