This is a new problem/bug introduced with the latest Quest 3 software update auto deployed last week.
Old workflow: When you have a link cable connected to your PC and you are trying to deploy a packaged build to your HMD via ADB, your normal workflow would be to double click a batch file which deploys your APK and OBB files with no further intervention. It's a fire and forget process.
Bug: If you do the old workflow, deploying your packaged build to the headset will time out and fail with the error message: "Did not find a bind listener".
Root Cause: The latest update causes a modal dialog box to pop up in the headset which says "Title: Switch to Controllers Body text: To use this app, please pick up your controllers and select Continue. Tip: Passthrough is a feature that lets you see your physical environment with you headset on. You can turn on passthrough now to find your controllers." This dialogue will FREEZE all other foreground and background actions, including any ADB file transfers on the headset until you pick up a motion controller and click the "continue" button. Once you click the continue button, the headset unfreezes and the file transfer continues. However, if you take off the headset or set down the motion controller, the motion controller will go to sleep in X number of seconds and the dialogue will pop up again and freeze all actions, including any background file transfers. This is extremely annoying and should never have passed QA.
Workaround: Before you deploy a packaged build to your headset via ADB, you must wake up your motion controller and click away any modal dialogue boxes. When you deploy a packaged build, you may put your finger on the face sensor, but keep an eye on the interior device display. If it goes dark, the modal dialogue box popped up again and you need to wake up the motion controller and click it away before your ADB file transfer times out. You have about 10-15 seconds to do this.
Long term fix: Meta needs to patch this in the next update so that this modal dialogue does not block background processes like an ADB file transfer. They could also just detect if the headset is in developer mode and just not display the dialogue box at all. The current state is a significant regression on quality of life for us developers.
I am also having this problem.. even if you use the SET_PROPRTY to disable_dialogs as described in the E2E testing docs, the modal prompt to switch to controllers still happens.
