Complications Appear Unnamed in Watch App After Syncing .watchface File

Question

Created 2w

Replies 2

Boosts 3

Participants 2

When using my app's complications with either Siri Intents or App Intents after syncing .watchface files, the complications appear without names in the iOS Watch app's complication picker. This leads to complications showing as blank entries without previews in the native watch app selector.

I'm using WidgetKit to create Watch complications with both approaches: AppIntents and Siri Intents.

We've tried multiple approaches with our WidgetKit watch complications:

Switching between IntentConfiguration and StaticConfiguration
Using different naming conventions for kind strings
Ensuring display names are properly set
Testing across different watchOS versions

But the result is always the same: after syncing .watchface files, our complications appear unnamed in the Watch app's complication picker. Is this a known limitation with .watchface syncing, a bug in the current implementation, or is there a specific requirement we're missing to maintain complication names during the sync process?

Screenshot 2025-03-11 at 21.05.05.png

Boost

Answer 1

DTS Engineer OP

Apple

6d

I see this a bug on the system side, and would suggest that you file a feedback report – If you do so, please share your report ID here for folks to track.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

1

Answer 2

AJcashmoney OP

5d

Thanks for the response. I agree this seems like a system-side bug and have filed a feedback report: FB16989845.

Additionally, due to this and other related issues, complication previews on iOS often don’t function reliably. Overall, WidgetKit for complications remains unstable, especially when used with .watchface syncing and Intent-based configurations.

0