Inactive Quest 3 cannot install Unreal 5 local Shipping Builds
Hey, just wondering if anyone else has run into this extremely weird Unreal installer issue on Quest: we're using Unreal 5.3, Quest 3 headsets, and running the stock "Install_[ProjectName]-Android-Shipping-arm64.bat" script for a locally packaged shipping build no longer installs successfully on the Quest 3 headset unless the headset is on, and has controllers active. Development and Test installations finish fine, active or inactive, it's just the Shipping build configuration with this issue. Shipping builds used to install fine when the headset was inactive, so it seems like this was introduced at some point with a recent OS update (or possibly something to do with AFS, since the old installers just used adb push, not an AFS server to push the OBB). Here's the output when trying to install to the Quest 3 when it's not active: Trying to start file server [packagename] Did not find a bind listener ERROR: Unable to connect to [device id] There was an error installing the game or the obb file. Look above for more info. Notes: If I put on the headset and pick up a controller, then run the installer, I see two quick blank black rectangles popup (like OS UI elements that start/stop in abrupt succession), and the installation finishes without incident. If I put on the headset and don't pick up a controller, I get a popup that tells me to "switch to controllers" when I attempt to install. Picking up the controller and clicking in time results in it finishing as well. Anyone else seeing this behavior/have any kind of workaround? (Other than obviously putting the headset on and waking the controller). I tried disabling body/hand tracking in case it was related, but didn't have an effect. It's not a huge deal once you know what to do, but we have a large team and not everyone remembers this kind of clunky way of getting a local Shipping build installed.1.1KViews4likes2Comments
