🐐🪢… 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

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)

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.

@choosetylernol I’m not even getting that far. The docker setup fails on the Mac. I can get my accessory code to compile on the RBP though. I have a build system were I use Xcode to edit and issue build-compile-run from Xcode to the PI. Can you use the Xcode debugger with the Docker setup (assuming Docker set works)? Otherwise I am not sure it offers much benefit and not worth the trouble.

@Documentation Engineer , so what you are saying is that a scene is a window on macOS?

or is a Window a Scene?

The rub with chip based security is that if the security model changes, your customers are stuck with a hardware solution that becomes potentially incompatible. With a software based solution, which I believe requires a server, then you relegate your customers to having to let the product talk to the public internet and having the public internet available at the time of setup. If your product works well on a closed network normally... not a good turn. We decided on hardware. This puts the onus on Apple to maintain backwards compatibility.