Post

Replies

Boosts

Views

Activity

Reply to Watchface Sharing Fails in TestFlight/AppStore on iOS/watchOS 26 (Works in Dev Builds)
We found the solution. For iOS/watchOS 26, you MUST: Migrate from the legacy Watch dual-target to a single-target. Generate the watch face file within your TestFlight build and bundle it with your app; do not generate it in a development environment. This ensures the complications are associated with a valid App Store ID. This strict validation appears to be new in iOS/watchOS 26, as it was not present in iOS/watchOS 18. Reference: Sharing Apple Watch Faces.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Oct ’25
Reply to Managing watch faces on paired Apple Watch
👍
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’25
Reply to Critical Bug in iOS 18.1 RC and watchOS 11.1 RC - WidgetKit Complications Not Syncing
Hello, I'm facing this issue on iOS/watchOS 26. Complications work in development(debug/release) but fail in TestFlight/App Store. Has anyone found a fix?
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Oct ’25
Reply to Watchface Sharing Fails in TestFlight/AppStore on iOS/watchOS 26 (Works in Dev Builds)
iOS app share: watchOS app share:
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Oct ’25
Reply to Watchface Sharing Fails in TestFlight/AppStore on iOS/watchOS 26 (Works in Dev Builds)
We found the solution. For iOS/watchOS 26, you MUST: Migrate from the legacy Watch dual-target to a single-target. Generate the watch face file within your TestFlight build and bundle it with your app; do not generate it in a development environment. This ensures the complications are associated with a valid App Store ID. This strict validation appears to be new in iOS/watchOS 26, as it was not present in iOS/watchOS 18. Reference: Sharing Apple Watch Faces.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Oct ’25