Hi Apple Developer Community,
I’m encountering an issue with complications (复杂功能) in my Apple Watch app after releasing it to the App Store. Here’s the scenario: During development and TestFlight testing, complications work correctly. Users can add the custom watch face from the iPhone and all complications display properly. After releasing to the App Store, when users try to add the same custom watch face from their iPhone, they see the error: “Complications Unavailable” (复杂功能不可用). However, if users add the watch face directly from their Apple Watch, complications load and work normally. Environment Details: watchOS: 26.3 iOS: 26.3.1 Xcode: 26.2 Distribution: App Store (release build) What I’ve tried so far: Verified that the complication data source is properly configured in the WatchKit extension. Confirmed that the app’s bundle ID and App Groups are consistent across debug and release configurations. Ensured that the complication entitlements and privacy permissions are declared in both iOS and watchOS targets. Tested with multiple devices and different Apple Watch models—the issue persists only when adding the watch face from the iPhone (App Store build). Key Question:
Could this be related to how the iOS-Watch complication handshake is validated in App Store builds? Or is there a known issue with complication availability when the watch face is added via iPhone vs. directly on the watch?
Any insights, debugging tips, or references to similar resolved issues would be greatly appreciated. Thank you!