beta 7 - still have this issue. On fresh install on iOS15 sync is working TO DEVICE. I can change data on iOS14 and macOS BigSur devices. All data is syncing down to iO15 device. After first change of data on iOS15 device sync for this device is fully stops (TO device and TO iCloud). Syncing for iOS14 devices keeps on working.

Still happening on beta 8. First change of data on iOS 15 device stops sync for this device in and out. Syncing for iOS 14 devices keeps on working. Release is near. It's frustrating...

talking small, I have one entity in my app with no relations. Still syncing stops for iOS 15 devices..

nitramluap I think I figured out the problem (in my case at least). So, initial state: iOS 14 and MacOS BigSur: Both for Development (installing app from Xcode 12.5.1 to device) and Production (installing app from TestFlight) synchronization works very well. Quick and accurately. iOS 15: For Development environment (installing app from Xcode 13 RC to device) synchronization work ALSO well. BUT for Production environment (installing app from TestFlight, app was submitted by both - previously Xcode 12.5.1, and now Xcode 13 RC) synchronization FAILS. It works just BEFORE first change of data on iOS 15 device. At first data changes on iOS 14 devices and MacOS BigSur are available on iOS 15 device, but then after first change of data on iOS 15 device it becomes out of sync - no changes are going to iCloud and no changes are coming from iCloud. At the same time synchronization for iOS 14 devices and MacOS BigSur keeps going on without issues... Because there was difference in Development and Production environments behavior, I've looked at my Schemas in CloudKit dashboard. There was a new field in Development Schema - CD_image_ckAsset, that wasn't there before (and I didn't do anything to add this field). I've Deployed changes in Schema in Production. After that my TestFlight app becomes alive in terms of synchronization on iOS 15 devices. Try to pay attention to Schema in CloudKit dashboard. If in your case you can't go even with Development environment, there also might be problems with fields in Schema.

BennetK. Ok, that’s sounds hopefully. In watchOS app I use .onOpenURL in ContentView - just like in iOS app. But there is no call to it when I tap on complication. I use the shared code for widgets for both iOS and watchOS apps (there I have widgetURL for the View). So there is no difference in the approach.

Actually, it’s better to pass an empty array of CLKComplicationDescriptor’s - just []. Apparently, there is no difference in the result. Moreover - passing some CLKComplicationDescriptor with displayName cause in appearing an empty complication with that name, which is not we want. So all we need is to implement a ComplicationController class with CLKComplicationDataSource conformance and empty methods (plus Info.plist key).

Actually, it’s better to pass an empty array of CLKComplicationDescriptor’s - just []. Apparently, there is no difference in the result. Moreover - passing some CLKComplicationDescriptor with displayName cause in appearing an empty complication with that name, which is not we want. So all we need is to implement a ComplicationController class with CLKComplicationDataSource conformance and empty methods (plus Info.plist key).

That’s exactly the solution, thanks! When this modifier came around?.. Was it available since the availability of PhotoPicker view? One thing - I guess we don’t have the ability to change the detends of the appearing picker as we have it for sheets?