So, what is the Apple recommended way in dealing with this? Using a type erased NSArray? @DTS Engineer

+1 Seeing the exact same issue The issue happens only on iPadOS 18. To reproduce the user has to open the popover on the iPad and then switch the app to the background (keeping the popover visible). Then the crash occurs. See FB16077587 for a sample project with instructions.

Thank you @Engineer! We were able to resolve the issue (in SwiftUI). The error was caused by presenting the PHPickerViewControllerRepresentable on an adaptiveSheetPresentationController that sometimes lead to the issue. We just had to remove the adaptiveSheetPresentationController and use a fullScreenCover instead. This fixed the issue.

Did you find the root cause, @evilmint45? I'm also facing this issue: https://forums.developer.apple.com/forums/thread/763520

The root cause of this issue that during the update of one view another update for the same view (and others) is triggered (cycle). So as described above you have to check what causes this cycle. To debug it : Start instruments. Under SwiftUI there's a row ‘View Properties’. Select it. Trigger the issue in the simulator and look at all updates that occur (you can switch between Summary, Updates, etc. when View Propertiesis selected). So you can find out which views or variables are being updated. Comment out the related updated views in SwiftUI and see which view and wich parts are causing it. Narrow it down by commenting out parts down your view hierarchy. When you have found the root cause. Find a way how to not trigger a cycle. In my case I used a UIViewRepresentableView with UIView.animate in the updateView(:) what was triggering the cycle.

@samliu_QPA, I'm receiving the same crashes and can not reproduce them. Have you found a solution to fix this or can give me any hint to find the root cause?

Please file a bug report at https://feedbackassistant.apple.com/ Until now, there are less than 10 bug reports reported for this issue. Otherwise it will not get fixed soon.

Same with SmartlookAnalytics, see FB11506040

@Anton Turvo, thank you very much for your comment! I can see the same error in Console: Trust evaluate failure: [leaf IssuerCommonName LeafMarkerOid SubjectCommonName] MacOS error: -67030 unrecognized status -67030 from codesigning library 0x16b7ab000 +[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:]: 75: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.97uVqY/extracted/VisionBoard.app/PlugIns/IntentsExtension.appex : 0xe8008001 (An unknown error has occurred.) 0x16b7ab000 -[MIInstaller performInstallationWithError:]: Verification stage failed The solution you proposed to modify the contents of project.pbxprojand adding CodeSignOnCopy didn't work for me. I'm still facing the above error. However, I have found a workaround by enabling Copy only when installing in the main target of the app in the Embed App Extensions (in Build phases section). So, the extensions are not copied to the iOS device and the error is resolved as well.

@jsnee I'm facing the same problem, please have a look at FB10962213

I have received the same error code 401 and it turned out that you need to wait up to 12-24 hours (in my case it was approximately 7 hours) after the creation of the private key until the verification succeeded with 200. Beyond this, you need to create a key for DeviceCheck and not for APN as stated by some examples. APN keys didn't work for me!

You could use caching player item and combine it with a cache.

Here is a workaround to resolve Key path value type 'WritableKeyPath<EnvironmentValues, WidgetFamily>' cannot be converted to contextual type 'KeyPath<EnvironmentValues, WidgetFamily>'. Source: https://stackoverflow.com/a/68489369 extension WidgetFamily: EnvironmentKey {     public static var defaultValue: WidgetFamily = .systemMedium } extension EnvironmentValues {   var widgetFamily: WidgetFamily {     get { self[WidgetFamily.self] }     set { self[WidgetFamily.self] = newValue }   } }

@edford, I can confirm seeing crash reports with 0x0 exception codes on iOS 15. My guess it is the watchdog killing the app, but I'm not sure. Please see FB9791707.

Btw, also for me the forum is very slow and I have a good internet connection and using a one year old Mac.