After Build & Run, nothing is installed on my Quest

Unity Engine
1

It literally stopped working from one moment to the other. One minute I was able to Build & Run my Quest game just fine, literally minutes later it stopped working.

I do a Build & Run which seems to succeed. After it has finished building, I get a window on the screen that it is deploying the package to the Quest 2. The window stays on the screen for a minute or so after which it disappears and my console says

UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

Build completed with a result of 'Succeeded' in 101 seconds (100501 ms)
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)```

But nothing is started on the Quest and if I check the installed apps, it's not there (yes, checked the "from unknown sources" section). Restarted my computer, restarted the Quest - nothing helped.

So what happened, and more importantly, how can I correct this? It was literally the last build I had to do before deploying to several Quests for an event tomorrow. So forgive me for panicking a little.
1 Like
2

I’ve tried to manually install the apk through the Meta Quest Developer Hud. It looks like it’s copying over the apk, then the progress bar disappears and the app does not appear in the list of installed apps. No error messages. But if I check the log files, I see this:

22:51:57.814
cutils
Failed to open(/data/misc/profiles/cur/0/com.EpicVR.TheChessMaster/primary.prof): No such file or directory
22:51:57.814
installd
Failed to prepare /data/misc/profiles/cur/0/com.EpicVR.TheChessMaster/primary.prof: No such file or directory
22:51:57.814
ArtManagerService
Failed to prepare profile for com.EpicVR.TheChessMaster:/data/app/~~UiJF1uGuwiYEhi8tfGl8hg==/com.EpicVR.TheChessMaster--zJS6Pi8E7gWXxk55ooWMQ==/base.apk
22:51:57.814
cutils
Failed to open(/data/misc/profiles/cur/10/com.EpicVR.TheChessMaster/primary.prof): No such file or directory
22:51:57.814
installd
Failed to prepare /data/misc/profiles/cur/10/com.EpicVR.TheChessMaster/primary.prof: No such file or directory
22:51:57.815
ArtManagerService
Failed to prepare profile for com.EpicVR.TheChessMaster:/data/app/~~UiJF1uGuwiYEhi8tfGl8hg==/com.EpicVR.TheChessMaster--zJS6Pi8E7gWXxk55ooWMQ==/base.apk```
3

I tried installing my backups (going back one build at a time). And it finally installed a month old backup which was the last version that didn’t use Vulkan. So apparently, for some reason my Quest will not install versions that use Vulkan anymore.

EDIT
I think that was the last version that used OpenGLES3 instead of Vulkan so I’m not 100% sure that is the problem

EDIT 2
Never mind. I tried building with OpenGLES3 only and it still wouldn’t install. So it has nothing to do with Vulkan/OpenGLES3

Then why those older version do install is beyond me. Or why versions that installed fine earlier today no longer install.

4

What about the usual “reboot everything!” approach?

Another thing to do on the Unity side is a full reimport-all, then a rebuild attempt, on the theory that some middle-step file is corrupt.

You can also use ClassyShark to look around the APK for differences. It might be something missing like an intent or activity or any one of those other silly Android things specified in the AndroidManifest.xml file.

5

Tried that. Didn’t work.

The problem is that an apk I had Build and Run just a few hours before, now all of a sudden no longer installs. So something on the Quest 2 has changed since that apk hasn’t.

I do remember the Oculus software running on my computer said something about new drivers needed to be installed and I just clicked the Ok button. I think that was the moment everything stopped working. I don’t remember exactly what the message said since I get messages like that often and I always let Oculus software update itself. So I don’t remember if it installed something on the Quest itself, or it just updated the Oculus software.

6

Ok, problem found.

Yesterday, I deleted the old version of my game on the Quest itself (by going to “Unknown Sources”, click the three dots next to the game’s name and click “Uninstall”). Apparently that doesn’t work properly and still leaves some “stuff” behind causing installing the apk again to fail.

So the solution was to run adb uninstall <package name>, even though the app is not listed in the list of “Unknown Sources”. This will completely delete all files still left on the device. After doing this, I was able to install the apk again.

8 Likes
7

It worked! Thanks

8

Thank you so much for this post. I had the exact same problem and it was driving me completely insane. Thank you thank you!!!

9

In case anyone is super new to this and not sure where to run that command from, it can be done as a Custom Command in the Oculus Quest Developer Hub’s Device Manager page. It’s the bottom-most section.

1 Like