I'm using Magisk 20.2 (20200) and Magisk Manager 7.5.0 (265) on an Android 10 device.
After I use "Hide Magisk Manager" to rename the app to "Manager", the renamed app when started prompts "Upgrade to full Magisk Manager to finish the setup. Download and install?" If I select "cancel', it exits. If I select "OK", it repeats the prompt.
It should just start normally instead of prompting in a loop.
I had the same issue when trying to reinstall Magisk Manager. I was able to work around it by uninstalling, reinstalling Manager 7.3.5 (from releases page), using that version to repackage, and then updating to 7.5.0.
Same issue on a Redmi 8 with Pie.
If reporting about issues, don't do "workarounds"... Reproduce the issue while grabbing a logcat so that @topjohnwu has something to work with!
No log, no fix...
I'm using Magisk 20.2 (20200) and Magisk Manager 7.5.0 (265) on an Android 9 device.
After I use "Hide Magisk Manager" to rename the app to "Manager", the renamed app when started prompts "Upgrade to full Magisk Manager to finish the setup. Download and install?" If I select "cancel', it exits. If I select "OK", it repeats the prompt.
I can confirm, have the same issue. Latest Magisk Stable, Android 9. Logcat: https://gofile.io/?c=iOHzr1
@Senliast thanks for the logs, here is the relevant line regarding this issue
01-04 22:01:50.048 5095 5095 D ziparchive: Zip: EOCD not found, /data/user_de/0/com.B.skGn.IaN7.isam/dyn/current.apk is not zip
@topjohnwu , what does it mean? What is the answer?
@topjohnwu no problem
Good to know I am not the only one with this problem (OnePlus 3T with Android 9)I will also try to make a raw of my logcat in the morning.
Same issue here as well. Tried to downgrade to the previous Magisk stable and still the same issue
The previous version does not work either (Asus Max pro M2 Android 9)
On Lineage os 17 it is the same :-(
Even i have same issue in OP6T & RN5 Pro
https://gofile.io/?c=mXt6Nu
Same issue here, Android 10, same log ziparchive: Zip: EOCD not found, /data/user_de/0/com.y8T.kqmzIWm.aU.W/dyn/current.apk is not zip
Same issue on OnePlus 6, lineage os 17. Magisk Manager 7.5.
current.apk
logcat(clip)
I remember seeing similar issue on v20.1 (and its corresponding Magisk Manager version). However, at that version, while it first asked me to upgrade to full Magisk Manager, pressing OK will enter the main screen and it never asked me again.
From what I remember, the issue is not present in earlier versions. Also, tardeaux's comment is probably correct as I'm currently on Magisk Manager 7.5.0, but the repacking was done on earlier versions, and it still works after upgrading to 7.5.0.
So it's probably an existing bug/regression that's been regressed even further. I couldn't test v20.2 at present, as it currently doesn't boot on my device.
I suspect the app renaming feature might have some issues as this time I renamed the Magisk Manager to something else that doesn't contain either Magisk or Manager, so this might have confused it.
I figured out the culprit, the stub APK is now updated and this issue should be fixed
Tested succesfully, renaming Magisk works, the app starts afterwards and also the banking app no longer detects Magisk after the rename
Issue is fixed, thanks John.
Issue is fixed, thanks John. Jeste艣 wielki, Polska si臋 k艂ania :)
@topjohnwu got same error keeps prompting to upgrade to full Magisk Manager. V 20.3 and latest apk.
magisk_log_20200131_154417.log
I am still facing the same issue. Tested on latest stable and the new canary build too.
@topjohnwu
i am with the same issue...
@jthreja @CooperTUGA Since the issue has already been solved for others, it's not clear to me how the issue you are facing can be addressed without further information. Perhaps it would help to provide logs.
Same issue here, when repackaging the App I get prompted for full install. I am using OP7p, latest android 10, current.apk (canary build), magisk 20.4.
My log is empty for some reason so posting it does not make much sense.
Without hiding and repackaging magisk manager works like a charm
Most helpful comment
I figured out the culprit, the stub APK is now updated and this issue should be fixed