Update: I added onAppear and onDisappear to every complication. Turns out that right before the memory crash, onAppear called for all of them, even for those that aren't present on any face. Clearly, the reason for memory crash is that all Views are loaded into memory simultaneously. I submitted Technical Support Issue to Apple.

@deeje, ha-ha, yeah. I also thought about it. Some unlucky clients will do all the chore :D

Looks like EXC_RESOURCE RESOURCE_TYPE_MEMORY has nothing to do with the bundle size, probably there's a memory leak or something.

Further exploration. I looked into intermediate objects in DerivedData... /Debug-watchsimulator/complicationsExtension.build/Objects-normal/arm64. The arm64 folder itself takes 25 MB. The fattest files are complicationsExtension.swiftmodule (1 MB) and complicationsExtension-master.priors (500 KB), everything else is hundreds of object files .o and other compiled stuff. Some complications are short files but they produce heavy objects. For example ClassicComplPulse.o is a 70-line SwiftUI view (with previews) and it results in 200 KB. The source code takes only 3 KB. Looks like SwiftUI views get significantly expanded after compilation.

Not completely sure but looks like users that are not logged into iCloud is a "_word" security role and they can only read.

So if the user isn't logged into iCloud we can't create records in the CloudKit database? This may fail business logic :(

I had similar problem too. I guess you should select a watch simulator as a run destination in order to build the previews for watchOS. It started since Xcode 15.

**Update: ** turns out CKQueryOperation.maximumResults is actually equals to 0, so the value is hidden. But the general idea is to give some way to split records in chunks so CKModifyRecordsOperation will not fail.

@MobileTen we do not discuss here how to wipe repository, good luck to find better application for your sparkling wisdom!

Same problem. This also leads to watch problem when I constantly see the message "Connecting to Uladzimir’s Apple Watch" then "Waiting Apple Watch to reconnect". I don't have Wi-Fi at home, my phone is used as Hotspot and I believe, that connection to Xcode via Network somehow disrupts the connection with Apple Watch.

I'm getting this error: xcrun: error: unable to find utility "devicectl", not a developer tool or in PATH Why don't I have devicectl installed?

I had the same problem with "Waiting to reconnect to Apple Watch" because I used Personal Hotspot. I got to go to cafe to join WiFi there and the issue was resolved. iPhone, mac and watch want to be in the same WiFi network and Personal Hotspot was always the issue, starting from very first versions of watchOS.

@jeremyhu, what is devicectl?

Same problem with CloudKit.

From documentation: Display a Placeholder Widget and Hide Sensitive Data A placeholder view is a generic visual representation with no specific content. When WidgetKit renders your widget, it may need to render your content as a placeholder; for example, while you load data in the background. It generates the placeholder using the redacted(reason:) view modifier with reason set to placeholder. This setting automatically renders the widget’s views in a way appropriate for use as a placeholder. To opt out of rendering as a placeholder and control which of your widget’s views appear redacted to hide sensitive information, use the unredacted() view modifier in the redacted(reason:) callback.