v13.6.0.r2212
v13.6.0.r2212
Changes since v13.6.0.r2211
🐛 Bug Fixes
1 distinct GitHub issue(s) referenced in this release.
📦 Recent Releases
🚀 Most recent major release — v13.6.0.r2202
Third-party apps that Shizuku+ grants permissions to (WifiList, App Ops, Hail, Tasker, and others) now reliably detect and connect to the service. Closed the last gap in the Cached Apps Freezer guard: a UserService's very first connect callback could be silently dropped if the client app was frozen in the background while its process was still starting.
⚠️ Most recent critical fix — v13.6.0.r2153
Releases r2141–r2152 all shipped the Drop-In build under the Plus APK's filename — anyone who installed "Shizuku+" in that window actually got moe.shizuku.privileged.api, which fails to install or update alongside stock Shizuku. Fixed by selecting release assets by verified applicationId instead of directory order.
| Release | Highlight |
|---|---|
| v13.6.0.r2212 (this release) | fix: don't force-stop clients on the live per-event binder delivery path (#371) |
| v13.6.0.r2211 | fix: restore retry-on-dead-provider for ordinary client binder delivery (#371) |
| v13.6.0.r2210 | fix: render release notes as actual Markdown instead of raw text |
| v13.6.0.r2209 | fix: bump api submodule to revert addFrozenStateChangeCallback (build r2208 failed) |
| v13.6.0.r2207 | fix: address ultracode review findings on the #371/#377 fixes (r2205/r2206) |