Yes, I am sure the Apple Watch app is not installed. I have Automatic App Install turned off, and I see it listed in the Watch app on iOS under the Available Apps section, which includes all the apps that are available but not installed.

Yeah, I've tried a lot of different things trying to replicate this. As annoying as some of the ClockKit stuff was, CLKRelativeDateTextProvider was great. The closest I got was some custom formatters and using a TimelineView to update the Text every second, but then that didn't work in the context of a complication (widget).

When you say "add your app intents directly to your app target" you mean just in a file that's part of the main app target, right? That's what I've been doing all along, but I still keep getting this error. I've stripped out all third party packages from my app and reduced it to just my one app target, and still the same issue. Also, I think I may have found you in the iOS Developers Slack... if you use that can you reply to my message there? I would love to ask you more so I can solve this.

Actually, this is wrong... it still wasn't working after this change. Instead, I determined the issue was that I had spaces in my Xcode project name.

Have you tried DTS about this? I am also wondering if I can do this. Also, thanks for your other posts about complications being broken after moving to single-target… I’ve been going through the same thing after making that change.

I was experiencing this problem with my app and following this thread for a while, so I wanted to note that I'm no longer seeing this issue on watchOS 10.1 (not beta). I'm advising any users who contact me about it to update to 10.1 to fix the issue.

I was experiencing this problem with my app and following this thread, so I wanted to note that I'm no longer seeing this issue on the public version of watchOS 10.1 (not beta). I'm advising any users who contact me about it to update to 10.1 to fix the issue.

Somehow it started working as expected again. Maybe it was updating to iOS 17.3?

Glad to know I'm not alone! I see the app can't accept invitations yet in the iOS 26 beta 1 release notes, so I hope that's fixed in beta 2. I'm more concerned about the lack of sessions or documentation about the changes to the API. Posted more about the missing names issue here. I wish I noticed this during WWDC so I could have done a lab to ask about it.

I reported the bug on FB18191886