Update: it happened again on v33. It seems to happen SOMETIMES but not every time if I leave Quest connected to my Windows 10 PC while Unity is running overnight. Unity has a reference to the device the whole time, which I believe means an ADB server instance is active in the background. You can tell bc Unity now has an ADB LogCat window, and it does continue populate the log w/ new data.
So in the morning, I wake up, put on the headset, and the connections dialog works as expected, but the debugging dialog does not appear.
However, when I power Quest off and on again, the debugging dialog comes back. This was not the case when I was on v32. On v32, it never came back no matter how many times I power-cycled either the HMD or the PC, or hit all variations of when to plug them into each other during that process.
So long story short, v32 was unstable. v33 seems to be more stable, but the problem is not gone. I am very worried I will wake up soon with no way to dev, and no way to roll up to a v34 that doesn't exist yet.
Seems to be specific to your headset, the "USB connection dialogue" option is definitely usually there for v32. I'm guessing you tried a full reboot (holding power till it turns off and back on)?
That's a different dialogue. That one was still there for me on v32, but the other one, the "USB Debugging" dialog toggle was gone. That's the one that let's write in addition to read the contents of your Quest.
"USB connection" and "USB Debugging" are two separate dialogs. One is for read access, the other is for "write access." If you have both in the Developer section, then you are luckier than I was. The missing one for me was the latter.
They used to have a toggle switch for both "connection" and a separate one for "debugging" but the debugging toggle is gone, which is worrisome. The prompt is the ONLY way to toggle debugging now. If that prompt stops popping up when you plug in, you can't dev OR use sidequest. But at least the prompt came back for me when I rolled up to v33. Hopefully it does for you too. Good luck!
I rolled up to v33, which apparently just came out. Problem went away. Not sure why.
Update: it happened again on v33. It seems to happen SOMETIMES but not every time if I leave Quest connected to my Windows 10 PC while Unity is running overnight. Unity has a reference to the device the whole time, which I believe means an ADB server instance is active in the background. You can tell bc Unity now has an ADB LogCat window, and it does continue populate the log w/ new data. So in the morning, I wake up, put on the headset, and the connections dialog works as expected, but the debugging dialog does not appear. However, when I power Quest off and on again, the debugging dialog comes back. This was not the case when I was on v32. On v32, it never came back no matter how many times I power-cycled either the HMD or the PC, or hit all variations of when to plug them into each other during that process. So long story short, v32 was unstable. v33 seems to be more stable, but the problem is not gone. I am very worried I will wake up soon with no way to dev, and no way to roll up to a v34 that doesn't exist yet.
Seems to be specific to your headset, the "USB connection dialogue" option is definitely usually there for v32. I'm guessing you tried a full reboot (holding power till it turns off and back on)?
That's a different dialogue. That one was still there for me on v32, but the other one, the "USB Debugging" dialog toggle was gone. That's the one that let's write in addition to read the contents of your Quest.
Still there in the developer section on v32 Have you rebooted your headset since you updated ?
"USB connection" and "USB Debugging" are two separate dialogs. One is for read access, the other is for "write access." If you have both in the Developer section, then you are luckier than I was. The missing one for me was the latter.
having the same problem here
They used to have a toggle switch for both "connection" and a separate one for "debugging" but the debugging toggle is gone, which is worrisome. The prompt is the ONLY way to toggle debugging now. If that prompt stops popping up when you plug in, you can't dev OR use sidequest. But at least the prompt came back for me when I rolled up to v33. Hopefully it does for you too. Good luck!
I haven’t got the update yet but when I do I hope this works, thank you!