-
Notifications
You must be signed in to change notification settings - Fork 139
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
MERGE APK Failed #116
Comments
is my java version too lower,use jdk17 is working |
@c01ns Reopening this and try to fix it. |
Similar error happens while using Tumblr APKM v35.8.0.110 from https://www.apkmirror.com/apk/tumblr-inc/tumblr/tumblr-35-8-0-110-release/tumblr-fandom-art-chaos-35-8-0-110-android-apk-download/ |
@c01ns @SubZero5 Jar is available at action run 10616226207 |
I am trying to shove the created APK file to ReVanced Manager but still giving errors on Tumblr v36.0.0.111 And here it's error log:
You may try it yourself... |
@SubZero5 Your case could be related to signatures block use flag |
Hi ~
Is this issue from APKEditor or ReVanced CLI? |
I don't know. Use |
The problem is with ZIP data descriptors, it's not a problem in the signature or AndroidManifest itself, but happens for all the files that are modified during merging I think (If you remove signature and preserve AndroidManifest.xml, same Data Descriptor presence mismatch exception thrown for resources.arsc). I thought this is a mistake in apksig, because the APK will work fine if you remove the exception, but it's not (well it might still be unnecessary validation, but as Maximoff (developer of Apktool M) noted, apksig does not throw this exception for merged APKs normally, only in ReVanced Manager/CLI, so he thinks it may be caused by something when patching). I don't know what exactly causes it or why, but I don't think this is a problem specific to APKEditor, because APKs merged by Apktool M and AntiSplit G2 have the same problem when patching with ReVanced. In AntiSplit M I simply removed the code from REAndroid which writes data descriptor, it works fine for merging, but I don't know if it would break other functions. |
Describe the bug
MERGE APK Failed
To Reproduce
Steps to reproduce the behavior:
00.005 I: [MERGE] Searching apk files ...
00.005 I: [MERGE] Found apk files: 3
00.065 I: [MERGE] Found modules: 3
00.129 I: [MERGE] Merging: com.GencSadiku.CarSimOpenWorld
00.131 I: [MERGE] Added [com.GencSadiku.CarSimOpenWorld] classes.dex -> classes.dex
00.131 I: [MERGE] Added [com.GencSadiku.CarSimOpenWorld] classes2.dex -> classes2.dex
00.215 I: [MERGE] Merging: UnityDataAssetPack
00.220 I: [MERGE] Merging: config.arm64_v8a
00.232 I: [MERGE] Sanitizing manifest ...
00.233 I: [MERGE] Removed-attribute : @0x0101064e
00.234 I: [MERGE] Removed-attribute : @0x0101064f
00.234 I: [MERGE] Removed-attribute : extractNativeLibs
00.234 I: [MERGE] Removed-attribute : isSplitRequired
00.235 I: [MERGE] Removed-element : name="com.android.vending.splits.required"
00.235 I: [MERGE] Removed-element : name="com.android.stamp.source"
00.235 I: [MERGE] Removed-element : name="com.android.stamp.type"
00.237 I: [MERGE] Removed-table-entry : res/xml/splits0.xml
00.237 I: [MERGE] Removed-element : name="com.android.vending.splits"
00.237 I: [MERGE] Removed-element : name="com.android.vending.derived.apk.id"
Exception in thread "main" java.lang.NullPointerException
at com.reandroid.arsc.chunk.xml.ResXmlElement.removeUnusedNamespaces(ResXmlElement.java:306)
at com.reandroid.arsc.chunk.xml.ResXmlDocument.removeUnusedNamespaces(ResXmlDocument.java:150)
at com.reandroid.arsc.chunk.xml.ResXmlDocument.refreshFull(ResXmlDocument.java:170)
at com.reandroid.apk.ApkModule.refreshManifest(ApkModule.java:130)
at com.reandroid.apkeditor.merge.Merger.run(Merger.java:87)
at com.reandroid.apkeditor.merge.Merger.execute(Merger.java:235)
at com.reandroid.apkeditor.Main.execute(Main.java:89)
at com.reandroid.apkeditor.Main.execute(Main.java:64)
at com.reandroid.apkeditor.Main.main(Main.java:36)
Log/Stacktrace
Used apk file
com.GencSadiku.CarSimOpenWorld
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: