Recent Oculus v63 update generates warnings in Unreal about dbgeng.dll / StackWalk2
Using Meta Quest Link App Version 63.0.0.216.361 (63.0.0.216.361) we are now seeing repeated warnings when loading an Unreal application (or even just the Unreal Editor). The Unreal application copies a version of dbghelp.dll across to the ThirdParty binaries folder, but this was always the case, and the warnings did not appear before the Oculus update. If the Oculus app is uninstalled, these warnings do not appear. Are any Oculus developers looking into this? Thanks. Possibly related to https://communityforums.atmeta.com/t5/OpenXR-Development/OpenXR-hand-body-tracking-extensions-not-working-over-AirLink-in/m-p/1155017#M725v63 - The wireless ADB debugging prompt shows a black screen.
Hi, Two tickets were opened here : https://communityforums.atmeta.com/t5/Get-Help/PTC-v63-The-wireless-debugging-prompt-does-not-appear-and-shows/m-p/1171644 and here https://communityforums.atmeta.com/t5/Get-Help/PTC-v62-The-USB-debugging-prompt-does-not-appear-when-the/m-p/1171979 But I was asked to post this here. To resume : On Q2, Qpro and Q3 (v62, v63) when the authorize WiFi debugging through adb prompt shows up, the Quest will first enter a black screen state. Then, we must click the home button on the right controller to make this window show. If I do not click the home button, it will remain in a black screen state. USB debugging prompt had same problem on v62 but it has been fixed on v63 thank to the new look/UI of the prompt. But the wireless debugging prompt have not been updated and still run into this problem. To fix the problem, Meta developers should update the wireless debugging prompt to the new look/UI.
