No Wireless Debugging pairing prompt on Quest 3

[TyGreeny]

Please check before submitting an issue

• I know what my device, OS and App Manager versions are
• I know how to take logs
• I know that generating a report, in whole part or in part, using AI/LLM is prohibited
• I know how to reproduce the issue which may not be specific to my device

Describe the bug

Attempting to use wireless debugging fails on Meta Quest 3.

To Reproduce

1. Activate Wireless Debugging in App Manager
2. Manually navigate to wireless debugging page in the settings.
3. Open the pairing code popup.
4. Open notifications in the Quest dashboard after App Manager finds the pairing request.
5. Click on the notification and attempt to pair.
6. Fail with no prompt for port or code.

Expected behavior

After clicking on the notification, there should be a prompt for the port and code.

Screenshots

No response

Logs

No response

Device info

• Device: Meta Quest 3
• Android Version: 14
• Quest OS Version: 2.4
• App Manager Version: 4.0.5
• Mode: No Root?

Additional context

Previously, I was able to get wireless debugging to work, but I cannot remember how.
When I tried before, there was no prompt for the code or the port.

[TyGreeny]

Okay, upon some more troubleshooting, it's back to a similar working state as before.
I followed these steps, some may be redundant.
Edit: Also during one of these steps, App Manager appeared in the paired Wireless Debugging list, not sure which one though.

1. Opened Meta Quest Developer Hub and enabled ADB over Wi-Fi.
2. Attempted to connect via the Wireless Debugging option in App Manager but failed.
3. Closed App Manager and its services and restarted the app.
4. Ran the 'adb pair' command on my computer.
5. Clicked the Auto option and connected via ADB over TCP but also froze.
6. Disabled ADB over WiFi in MQDH, then repeated step 3 and restarted the headset.
7. Upon reopening and selecting the Wireless Debugging option, it now automatically connects after each startup.

[MuntashirAkon]

I'm not sure if notification reply is supported in Quest. ADB over TCP and Wireless Debugging uses the same method once the pairing is completed. So, the latter works.

[TyGreeny]

I'm not 100% certain it's unsupported, however, I haven't seen an app that enables a reply within the notifications. It does allow an action from the notifications, just not the reply prompt.

Permission Manager X has a workaround though, it scans for the port and prompts for the pairing code within the app rather than the OS.

[MuntashirAkon]

Permission Manager X has a workaround though, it scans for the port and prompts for the pairing code within the app rather than the OS.

That's what we did too in the past. But in a regular phone, a user needed to use a split view since the pairing code disappears when the user leaves that window. Don't know if that's also the case for Quest 3.

[TyGreeny]

By default the Quest 3 allows for something akin to split screen. Multiple flatscreen apps and 1 "immersive" app.

When testing in Permission Manager, it didn't have any issues with keeping the code/port and allowing me to input the code/port.

[MuntashirAkon]

By default the Quest 3 allows for something akin to split screen. Multiple flatscreen apps and 1 "immersive" app.

Thanks. This basically means that I need to selectively bring back the old dialog-based pairing.