Thanks, never would've figured this out. Upvoted your comment.

I don't think that's true. They can be compiled from the app target, but it's not required. In our case we have a lightweight Intent Target that fetches data from CoreData and returns what's requested.

Thank you Keith! I'll give it a go and see of things improve

Hi, I'm also wondering if the possible errors are listed somewhere? Would make it much easier to write unit tests and ensure everything is working as intended :)

I haven't had any troubles requesting authorization. Sorry to hear it isn't working as expected for you.

Did you get any response on this issue?

Correct, I added these changed to the Watch app Info.plist Here's a feedback as requested: FB14608566

It's been confirmed to be a bug, mentioned in the release notes for the latest beta Tapping Live Activity does not launch watch apps that use the WKSupportsLiveActivityLaunchAttributesTypes Info.plist key. Instead, a Live Activity tap displays the full-screen view with an “Open on iPhone” option. (132832577) (FB14568721) https://developer.apple.com/documentation/watchos-release-notes/watchos-11-release-notes

I've read through the code carefully and added logs of meta data that might explain the exception. Haven't found a solution yet. A sysdiagnose might make things easier, but we have no way to communicate with specific users. My current best guess is that the NSManagedObject property "id" becomes nil for two objects at the same time. When "id" is nil, I return an empty string. So if this occurs at the same time for two objects, we have duplicate objects.

I can no longer reproduce it in iOS 18.2, can you?

If this enum does only refer to the mini-player in these two different states I assume it's up to me to create a view and a custom animation with associated ShapeTransition between the mini player and the full screen player. Is that right?