Won't install on Quest 3

[c-hri-s]

Because of the changes to permissions (you first need to create folders before copying items into them), the script fails to install on a Quest 3 headset

[KaladinDMP]

Thank you, yes I also found this out tonight. I'll update it in the next few days, I don't have a quest 3 myself but I think adding one command should do it.

[c-hri-s]

Thanks! I'm happy to test anything if needed, I've got a Quest 3 here.

[KaladinDMP]

Please check the new release (Pre release) and let me know how it goes, i dont own a 3 myself so provided 2 similar fixes in hopes 1 or both does the trick

[c-hri-s]

v1 failed:

Now lets install Quest App Launcher
* daemon not running; starting now at tcp:5037
* daemon started successfully
Performing Streamed Install
Success
adb.exe: unknown command mkdir
adb: error: failed to copy 'aaa.QuestAppLauncher.App\cache\UnityShaderCache\026d269b040fad1a508c263f822bcbec' to '/sdcard/Android/data/aaa.QuestAppLauncher.App/cache/UnityShaderCache/026d269b040fad1a508c263f822bcbec': remote secure_mkdirs failed: Operation not permitted

Press any key to continue . . .

v2 failed also:

Now lets install Quest App Launcher
* daemon not running; starting now at tcp:5037
* daemon started successfully
Performing Streamed Install
Success
adb.exe: unknown command mkdir
adb: error: failed to copy 'aaa.QuestAppLauncher.App\cache\UnityShaderCache\026d269b040fad1a508c263f822bcbec' to '/sdcard/Android/data/aaa.QuestAppLauncher.App/cache/UnityShaderCache/026d269b040fad1a508c263f822bcbec': remote secure_mkdirs failed: Operation not permitted

Press any key to continue . . .

[KaladinDMP]

Wow im dumb, think i see the issue for some reason i forgot to add shell to the command, im uploading the updates now please retest at your convenience.... this should work tho

[c-hri-s]

Test with QAL.Autoinstall.v0.5.-DMP.7z

It installed okay - but all I see when I run the app is the blue settings cog.
If I click the cog, I see the settings window, but the main window of apps/games isn't shown.

This was what happened when I installed it manually, but I'd assumed I screwed up the install.
Looks like some issue with the loader with the Q3 perhaps.

[KaladinDMP]

Hmmm the others i had testing had the same thing happen on autoinstall but manual install worked for them so thats very weird. They just sideloaded the APK and then manually moved the aaa.questapplauncher.app folder into android/data ... i cant figure it out im sorry. Do you use Rookies Sideloader? i have a sideloader version too which no one has tested. Im guessing it should work on rookies 2.24 beta tho

[KaladinDMP]

My friend had an idea to move the apk to last im gonna upload this one last thing .... if you can test please

[c-hri-s]

Sure I can test. Yep I have Rookies too.

[c-hri-s]

Same behaviour with that new version

[SavageCore]

0.5 installs OK but nothing displays when launched. When updating the games/apps, it results in an access denied error.

Is there a better way to see this logline? It has to do with the icon pack. Probably QAL issue itself based on new permissions? Like BMBF selecting the folder and giving permissions to it...

[KaladinDMP]

0.5 installs OK but nothing displays when launched. When updating the games/apps, it results in an access denied error.

Is there a better way to see this logline? It has to do with the icon pack. Probably QAL issue itself based on new permissions? Like BMBF selecting the folder and giving permissions to it...

your on quest 3 too? totally different issue then the other guy and i dont own a quest 3 lol. Just gonna delete .5 and go back to the one that works for quest 2 and also link the rookies version under releases.

About your logline thing i that picture is so tiny i cant even see what you mean, maybe use imgbb or something instead of github? to put the pic up