compileSdkVersion value changed in AndroidManifest.xml file
See original GitHub issueInformation issue #1852 #1909
After decompiling and recompiling with apktool, the contents of the AndroidManifest.xml file are changed as follows. 0. 2.3.3 version works as normal.
- Apktool Version (
apktool -version
) - 2.3.4 & 2.4.0 - Operating System (Mac, Linux, Windows) -Windows10
- APK From? (Playstore, ROM, Other) - Other
Steps to Reproduce
- original : AndroidManifest.xml -> android:compileSdkVersion=“28”
- delete framework(1.apk)
- ‘d’ option ->
- ‘b’ option ->
- Check the AndroidManifest.xml file. AndroidManifest.xml -> android:compileSdkVersion=“23” compileSdkVersion changed
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. sample_compilesdkversion.zip
Questions to ask before submission
- Have you tried
apktool d
,apktool b
without changing anything? Yes. - If you are trying to install a modified apk, did you resign it? N/A
- Are you using the latest apktool version? Yes. 2.3.4 & 2.4.0 version
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:16 (4 by maintainers)
Top Results From Across the Web
Why does Android Studio throw errors in the manifest file ...
I changed the compileSdkVersion & targetSdkVersions in app gradle file from 26 to 23. I clicked sync now. It resulted in 7 error...
Read more >CompileSdkVersion and targetSdkVersion — what is the ...
In this article, we'll take a closer look at two values that are set in the build.gradle file: compileSdkVersion and targetSdkVersion.
Read more ><manifest> | Android Developers
The value of the package attribute in the APK's manifest file represents your app's universally unique application ID. It has to be formatted...
Read more >Picking your compileSdkVersion, minSdkVersion ... - Medium
It should be emphasized that changing your compileSdkVersion does not change runtime behavior. While new compiler warnings/errors may be ...
Read more >Get Started | Android - Google Developers
Use Android Studio 3.2 or higher · Make sure that your app's build file uses the following values: A minSdkVersion of 19 or...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same problem here, compileSdk changed from “9” to “6.0-2438415” with apkTool 2.3.4 or 2.4.0. But no problem with apkTool 2.3.3 (compileSdk not modified) so regression seems be in 2.3.4 version.
Old
Rebuilt
Indeed changed (aapt1).
Let me try aapt2.
Nope, still busted. Marking as bug.