I have the exact same issue as Danny182. Before transfering the application (that contains a share and a notification server extension), the value for the com.apple.developer.ubiquity-kvstore-identifier entitlement key for the main app and the two extension targets was OldTeamIdentifier.KVSIdentifer. Post transfer, the value that got automatically assigned by Apple in the "iOS Team Provisioning Profile" (managed) for the main application is something like: OldTeamIdentifier.NotificationServiceIdentifier and for the two extension targets the value for that key is NewTeamIdentifier.*. That means that if I issue an update using the new provisioning profiles for my app now, the KVS functionality will certainly break as: All of the targets (both the main application and the extensions) point to a KVS identifier that does not exist, thus anything stored there will be inaccessible to the users. The main application target points to KVS identifier 1 and the share and notification service extension targets point to KVS identifier 2. Given that for the extensions the value has a wildcard (*) suffix, I can replace it with NotificationServiceIdentifier but I can't change the NewTeamIdentifier to the OldTeamIdentifier, making it impossible to match the value of the main app. Any ideas? Do I need to contact an Apple engineer for this?

Update Just noticed that when the user adds contacts to their 'Selected Contacts' list, the application gets killed by the OS, so that's solved. When they remove contacts from that list though, the OS doesn't kill the application, so the logic will still display and allow user to interact with contacts that they have since disallowed. I have also noticed that if I issue a CNChangeHistoryFetchRequest when the application becomes active after the user has removed some of their 'Selected Contacts', then the CNFetchResult will include as many CNChangeHistoryAddContactEvent as the contacts that are allowed after the removal. The value of the currentHistoryToken property does not change. Is this the proper way of detecting deletions on the 'Selected Contacts' list?

Something's that is also interesting is that when I set the kVTVideoEncoderSpecification_EnableLowLatencyRateControl flag during the creation of the compression session, then if I attempt to query back the value of the kVTCompressionPropertyKey_UsingHardwareAcceleratedVideoEncoder flag using the code I pasted above, I get an error (-12900 kVTPropertyNotSupportedErr), which it's either wrong or it means that the low-latency mode does not support hardware acceleration?

Just noticed that I forgot to post the code that queries the value of the kVTCompressionPropertyKey_UsingHardwareAcceleratedVideoEncoder flag: if (@available(iOS 17.4, *)) { CFTypeRef value = NULL; OSStatus result = VTSessionCopyProperty(session, kVTCompressionPropertyKey_UsingHardwareAcceleratedVideoEncoder, kCFAllocatorDefault, &value); if (result == noErr) { NSLog(@"value: %@", value); } }

If you undo your fix and look at your app in Activity Monitor, what do you see? You are right: The iOS app shows up as 'Intel' kind in the Activity Monitor while the Simulator app shows up as 'Apple' kind. Thanks Quinn!

I believe you are right. My host machine is indeed a Macbook Pro (14-inch, 2021) that has the M1 family chip. On my Xcode project, I was excluding the "arm64" architecture for the simulator devices due to some old dependencies via the "EXCLUDED_ARCHS[sdk=iphonesimulator*]" = arm64; flag. As far as I can understand, this was triggering the simulator processes to spawn under Rosetta emulation, although this was not shown somewhere. Even the Activity Monitor window displayed 'Apple' instead of 'Intel' in the 'Kind' column: When I removed the "EXCLUDED_ARCHS[sdk=iphonesimulator*]" = arm64; flag, adjusted my dependencies and re-run the app on the Simulator, I was able to open the QuickLook preview controller without a crash, so I assume that this flag was to blame here. As a general question, is there a way to know whether the simulator instance runs under Rosetta emulation?

Hello Quinn, I have temporarily removed Sentry, re-tested and it still crashes. Please find the updated crash report attached. SSSSSS PPPPP 4-4-22, 14-25.crash

Hey Quinn! I am attaching the full crash report in this answer: SSSSSS PPPPP 1-4-22, 09-07.crash