Close, but not quite right; this is still correct:I did not find where it was mentioned but, basically release is the 'lite' version.
The debug version is the 'heavy' version including extra logging and more for debugging the Magisk build.
I might be wrong but..
Both canary (release) and debug are released at the same time and John does not specify a difference between the two.
They both point back to the latest commit at the time of their release.
Magisk [GitHub] - Release new canary build
magisk-files [GitHub] - Update Canary Channel: Upstream to 9183a0a6
magisk-files [GitHub] - Commit history.
So I assume the current debug version is still just the debug version of the canary build.
The current Magisk build script.
./build.py --help
Code:usage: build.py [-h] [-r] [-v] [-c CONFIG] {all,binary,app,stub,emulator,avd_patch,clean,ndk} ... Magisk build script optional arguments: -h, --help show this help message and exit -r, --release compile in release mode -v, --verbose verbose output -c CONFIG, --config CONFIG custom config file (default: config.prop) actions: {all,binary,app,stub,emulator,avd_patch,clean,ndk} all build everything binary build binaries app build the Magisk app stub build the stub app emulator setup AVD for development avd_patch patch AVD ramdisk.img clean cleanup ndk setup Magisk NDK
Cheers.![]()
Just a minor note: Magisk Canary is now app-release, not app-debug...
If you installed app-debug, you're either on an old Canary build, or you've installed new Debug instead of Canary...
The 'debug version of the canary build' (built with debug build flag) is not now considered 'Canary', but 'Debug', and not suitable for daily use...
The Canary designation has been re-purposed for builds built with release build flag and deemed suitable for daily use...
Previously, only workflow files built with debug build-flags were supplied to Canary ( https://github.com/topjohnwu/magisk-files/tree/canary ) repo (although likely files built with release flags were actually produced). Ie. we had:
... We now have:
supplied.
The change is that app-debug.apk has become the package for the new Debug channel (ie. it is no longer 'Canary' per se), and app-release.apk is now the new Canary... John clarified that 'Canary is now built as release'...
Confusion probably comes from the fact that the magisk-files canary-tree repo is still used for both, but this of course makes sense considering they are always synced builds produced in tandem so that Debug is simply the debug build of new Canary releases with a new name. (Actually the notes.md file is shared at present)...
This can also be seen by examining the JSON sets at https://github.com/topjohnwu/magisk-files
where canary.json calls app-release.apk and debug.json calls app-debug.apk, but these are the same synced builds hosted at a common URL per commit...
As mentioned, Canary can be used for daily use going forward, but 'Debug builds should only be used if you are actively developing Magisk, or if you want to submit bug reports'. Especially once proposed changes (adding symbols and maybe some sanitizers, and enabling core dumps on debug executables for better debugging and auditing) are made, Debug should not be used daily. 'These changes can be an issue on older devices, and could significantly affect performance'
www.twitter.com/topjohnwu/status/1525753967954628608

Last edited: