Ah this finally worked and I did not have to unpair the watch from the iPhone. It seems like the key is to disable developer mode on the iPhone and then restart both devices. Now my watch is back in the list of my devices. And it seems like this has also fixed the other issue that Xcode is unable to connect to the watch: https://forums.developer.apple.com/forums/thread/734694?page=2

I agree the bug resurfaced for me as well...

I can't check, because the Preferences app crashes always on my iPhone 15 Pro, iOS 17.0 simulator 🤷‍♂️

That is something I did not think about so far. I think that is not case. I don’t have any pre-compiled 3rd party frameworks in there. It’s all open source and compiled from Swift directly. I guess the compiler would discover incompatibilities here.

According to the documentation this should not be necessary. I just want to access public information. Using the Apple Music Web API with a developer key and a JWT works fine. But when I want to use the MusicKit, it seems to require the authorization also for publicly accessible information. When I call the .request() API the user gets a prompt even when I do not access their library. I guess when using MusicKit authorization is always required and the fallback is to use web api directly?

I got a reply from Apple on the feedback. Apparently the CustomLocalizedStringResourceConvertible is the right way to do it. It was documented on a WWDC video, but it’s not mentioned in the SDK documentation

There is no real process, but for WWDC22 it was possible to just share the invite email with my colleague and to ask the Apple engineer if he could join in the meeting.

Partially disabling it works as well. I'm not sure which part needs to be disabled, but this setting works: Configuration: Apple Internal: disabled Kext Signing: disabled Filesystem Protections: enabled Debugging Restrictions: disabled DTrace Restrictions: disabled NVRAM Protections: disabled BaseSystem Verification: enabled