Shizuku permission prompt appears every time VInstall is opened (v0.4.3)

[DreDay10000]

Device & OS
• Device model: Samsung Galaxy S9+
• Android version: Android 10
• VInstall version: 0.4.3

Bug
After updating to VInstall 0.4.3, every time I launch the app it shows the “Allow Shizuku permission” prompt again.

I grant the permission once during that session and everything works normally, but the next time I open VInstall the prompt re-appears (exactly once per launch).

Expected behavior
The Shizuku permission should only be requested once (the first time the app needs it). After granting it, the prompt should never appear again on future launches.

Actual behavior
Prompt appears on every single app launch.

Steps to reproduce

1. Grant Shizuku permission to VInstall (via the prompt or in the Stellar app).
2. Close VInstall completely.
3. Re-open VInstall.
4. The Shizuku permission prompt appears again.

Log
2026-04-13-02-37-45_618.zip

Additional notes
This started immediately after updating from 0.4.2-hotfix2. The old crashing issue seems resolved in 0.4.3.

Let me know if you need me to capture any additional logs, try a specific reproduction step, or test anything else!

[lenzarchive]

Hey, thanks for the detailed report and the log! XD

So I looked into it and yeah, found the issue. Basically the app checks the Shizuku permission too early on launch before everything's properly connected, so it always thinks the permission isn't granted yet even though it already is. That's why the prompt keeps showing up every single time. :b

Already know the fix for it, just a bit busy right now so I'll get to it later today around 11.30 to 13.50 (GMT+7). Will push it once I have the time! :)

Thanks again for the report, really appreciate it. :D

[lenzarchive]

Good afternoon and hey again! Looks like I've already worked on and patched the issue you ran into, could you try this debug build before I release it as a hotfix? :D

Download:
GDrive: https://drive.google.com/drive/folders/1y5Mk3ZIi4NrBtG6kvIihVB7Mukanbab8?usp=drive_link

Thanks a lot for the detailed breakdown of the behavior and the repro steps XD

[DreDay10000]

Same bug. Prompt appears after every app launch again. Perhaps this has something to do with the Stellar app?

[lenzarchive]

Hey! I've finally figured out the issue, turns out it's coming from Stellar itself XD

But don't worry, I've added a "Request Permission" button just in case the Shizuku prompt doesn't show up. This is pretty normal actually, since Shizuku isn't only used by one app, a lot of other apps use the Shizuku API too, so the prompt doesn't always appear automatically :)

Now, if you see a "Shizuku permission denied" message, try checking the app's permission first. If it's set to "Deny", just switch it to "Ask" or go straight to "Allow" for a quicker fix.

Oh and one more thing, would you mind trying this debug build before I release it as a hotfix? Thanks a lot, your contribution really means a lot! :D

Download:
GDrive: https://drive.google.com/drive/folders/1O52-2SPS5ChxW1oR_DTjOUHwA3qbZv1N?usp=drive_link

[DreDay10000]

Update: New build is a bit better. This time VInstall is prompting every 2nd app launch. So basically every other opening of the VInstall app, VInstall continues to make requests for Shizuku permission.

[lenzarchive]

Hey, sorry for the late reply on this! Could you try this new debug build again? Based on the issue you reported :D

Download: https://drive.google.com/drive/folders/1rsosg683man4Pd0cUgAqfahBE1c2XG_X?usp=drive_link

[DreDay10000]

Update: Now you have a secondary issue... When setting the install mode to Shizuku, the app does not perceive it active/permitted. Here's the log:

[06:39:50.810] D/MainActivity: renderState: Idle
[06:39:50.820] I/MainActivity: Application started
[06:39:57.770] D/Settings: Mode UI updated: SHIZUKU
[06:40:09.736] I/MainViewModel: File selected: accrescent-0.28.1.apk format=APK
[06:40:09.852] D/MainActivity: renderState: FileLoading
[06:40:09.980] D/MetadataReader: readApkFile: pkg=app.accrescent.client ver=0.28.1 label=Accrescent icon=true
[06:40:10.013] I/MainViewModel: SHA-256: 40f97ac3ee659d8b1f91dba8b84449fe3c14e05c1e82754375252d8746e6b1f5
[06:40:10.015] D/MainActivity: renderState: FileSelected
[06:40:11.845] I/MainViewModel: Starting installation mode=SHIZUKU format=APK
[06:40:11.855] D/ApkInstaller: install: content://com.android.externalstorage.documents/document/0FCB-DAC5%3AAndroid%2Fdata%2Forg.freedownloadmanager.fdm%2Ffiles%2FFDM%2Faccrescent-0.28.1.apk
[06:40:11.878] D/ApkInstaller: Cached: /data/user/0/com.vinstall.alwiz.debug/cache/install.apk
[06:40:11.883] I/SplitInstaller: Install mode: SHIZUKU, files: [install.apk]
[06:40:11.883] E/SplitInstaller: SHIZUKU mode selected but Shizuku is not active/permitted, falling back to session
[06:40:11.884] D/SplitInstaller: installViaSession: 1 file(s)
[06:40:11.900] D/MainActivity: renderState: Installing
[06:40:13.611] D/SplitInstaller: Writing install.apk (6954309 bytes)
[06:40:13.974] D/SplitInstaller: Session committed, id=2067460629
[06:40:13.975] D/MainViewModel: Waiting for installation result...
[06:40:13.988] D/InstallReceiver: status=-1 msg=null
[06:40:13.988] D/InstallReceiver: Pending user action
[06:40:21.361] D/InstallReceiver: status=3 msg=INSTALL_FAILED_ABORTED: User rejected permissions
[06:40:21.362] I/InstallReceiver: Install cancelled by user
[06:40:21.362] D/InstallHelper: emit: Failure(message=Installation was cancelled)
[06:40:21.364] I/MainViewModel: Install result: Failure(message=Installation was cancelled)
[06:40:21.372] D/MainActivity: renderState: Cancelled

[lenzarchive]

how about this new build? 🤔

Download: https://drive.google.com/drive/folders/1C6DLTN3FyaRLtqLgYVY7dVkcxRDYoliW?usp=drive_link

[DreDay10000]

Log:
[03:53:40.405] D/MainActivity: renderState: Idle
[03:53:40.415] I/MainActivity: Application started
[03:54:12.045] I/MainViewModel: File selected: accrescent-0.28.1.apk format=APK
[03:54:12.159] D/MainActivity: renderState: FileLoading
[03:54:12.289] D/MetadataReader: readApkFile: pkg=app.accrescent.client ver=0.28.1 label=Accrescent icon=true
[03:54:12.323] I/MainViewModel: SHA-256: 40f97ac3ee659d8b1f91dba8b84449fe3c14e05c1e82754375252d8746e6b1f5
[03:54:12.326] D/MainActivity: renderState: FileSelected
[03:54:23.375] I/MainViewModel: Starting installation mode=SHIZUKU format=APK
[03:54:23.380] D/ApkInstaller: install: content://com.android.externalstorage.documents/document/0FCB-DAC5%3AAndroid%2Fdata%2Forg.freedownloadmanager.fdm%2Ffiles%2FFDM%2Faccrescent-0.28.1.apk
[03:54:23.401] D/ApkInstaller: Cached: /data/user/0/com.vinstall.alwiz.debug/cache/install.apk
[03:54:23.405] I/SplitInstaller: Install mode: SHIZUKU, files: [install.apk]
[03:54:23.406] E/SplitInstaller: SHIZUKU mode selected but Shizuku is not active/permitted, falling back to session
[03:54:23.407] D/SplitInstaller: installViaSession: 1 file(s)
[03:54:23.418] D/MainActivity: renderState: Installing
[03:54:25.614] D/SplitInstaller: Writing install.apk (6954309 bytes)
[03:54:26.041] D/SplitInstaller: Session committed, id=441440549
[03:54:26.042] D/MainViewModel: Waiting for installation result...
[03:54:26.065] D/InstallReceiver: status=-1 msg=null
[03:54:26.066] D/InstallReceiver: Pending user action
[03:54:44.011] D/InstallReceiver: status=0 msg=INSTALL_SUCCEEDED
[03:54:44.012] I/InstallReceiver: Install SUCCESS
[03:54:44.013] D/InstallHelper: emit: com.vinstall.alwiz.installer.InstallHelper$Result$Success@a3ead78
[03:54:44.017] I/MainViewModel: Install result: com.vinstall.alwiz.installer.InstallHelper$Result$Success@a3ead78
[03:54:44.019] D/MainActivity: renderState: Success

[lenzarchive]

Hmm, it seems like it's still not working properly, right?
Could you check the permissions for "com.alwiz.vinstall.debug" and the Stellar app version?

Because I'm using the latest version of Stellar which is v1.0.14, and please upgrade the app if you're still on an older version, since when I tried it on native mobile devices (Samsung A06, Poco X3 Pro, and Itel Vision 3) and an emulator (BlueStack 5), VInstall was able to detect Shizuku as active :D

Once it's working properly, please let me know! XD

Thank you and sorry that I wasn't able to resolve it properly on my end :)