Forum Discussion
app keeps stopping/adb no longer recognized in Quest
I suddenly - in the past two months - after firmware update? cannot get a build to run on the Quest.
I'm running Unity 2019.1.5f with Windows 10. There are five Depthkit captures in my scene, which built previously, without any issue.
Now it won't launch at all. I immediately get a message in the Quest that says the app has stopped. When I click the option to open app again, it tells me the app keeps stopping. Unable to test.
Can someone please help with this? I have read through all of these posts, tried updating adb drivers, turning developer mode on/off, etc. etc. and my Quest is essentially useless.
The Quest shows as connected in the Unity build window. Shows in my devices as "quest" and when I start the build, changes to MTP...?? I've gone into device control and tried to update according to instructions posted by others on the forum, but without luck.
I have lost so much time - not sure how to proceed with my VR project....
I'm running Unity 2019.1.5f with Windows 10. There are five Depthkit captures in my scene, which built previously, without any issue.
Now it won't launch at all. I immediately get a message in the Quest that says the app has stopped. When I click the option to open app again, it tells me the app keeps stopping. Unable to test.
Can someone please help with this? I have read through all of these posts, tried updating adb drivers, turning developer mode on/off, etc. etc. and my Quest is essentially useless.
The Quest shows as connected in the Unity build window. Shows in my devices as "quest" and when I start the build, changes to MTP...?? I've gone into device control and tried to update according to instructions posted by others on the forum, but without luck.
I have lost so much time - not sure how to proceed with my VR project....
2 Replies
- I am having the same problem now. Anyone have an answer? a Debugging pipeline?
Having the same issue. I can run the exact same build just fine on a consumer Quest 1, but it immediately quits after launching on an OFB Quest 2
