So to regain the functionality, I first set the Derived folder to be relative to the project so the build product does not end up going somewhere else. Then I add the "Products" folder to the project file and uncheck all the targets so it is a reference-only. The rub is that the non-debug is apparently built elsewhere. How nice to waste time hunting down the output of this too.

All the web documentation on developer mode, be it Apple's or otherwise, seems to be inaccurate now. Developer mode cannot be found on the iPhone, iPad, Apple Vision Pro or Mac currently under the released OSs as of 12-June-2024. An Apple systems engineer and I are searching for answers on this (they were investigating before I called them). It makes WWDC2024 taste like a Coke gone flat and warm without being able to dev with the new ideas against your devices. (ruins the WWDC experience frankly)

🐐🪢… Developer Mode does not appear until you have paired your AVP with your Mac in Xcode. This is presuming you are trying to get the UDID of the goggles for the developer registration of the device in the developer portal. This appears to be called "Identifier" instead of UDID as the other documentation specifies in the portal. AVP: Open Settings -> General -> Remote Devices on the AVP which will show it is ready to pair Mac: Open Xcode -> Windows -> Devices and Simulators to see the goggles in the left bar Pair and follow all the prompts flipping back and forth for another 13 steps in this dance

I changed the build products location from the default to project relative. This caused the "Command CodeSign failed with a nonzero exit code". When I changed the build products location back to the Derived Data folder (default location for Xcode) the build had no errors. I tried to delete the build products from the new location but it did to matter. I had to use the Xcode default or it broke my project. I am using Xcode26 beta.