Posts

Post not yet marked as solved
2 Replies
666 Views
This is a very annoying error which is causing a crash in my app. The error description is very vague and I'm guessing mostly related to oddities of Xcode 15 Beta. Here is the full error stack: *** Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', reason: 'Could not instantiate class named _UIRecessedMaterialView because no class named _UIRecessedMaterialView was found; the class needs to be defined in source code or linked in from a library (ensure the class is part of the correct target)' *** First throw call stack: ( 0 CoreFoundation 0x00007ff80048c88a __exceptionPreprocess + 242 1 libobjc.A.dylib 0x00007ff800057894 objc_exception_throw + 48 2 CoreFoundation 0x00007ff80048c768 -[NSException initWithCoder:] + 0 3 UIFoundation 0x00007ff804a1eb4d UINibDecoderDecodeObjectForValue + 352 4 UIFoundation 0x00007ff804a1eebe UINibDecoderDecodeObjectForValue + 1233 5 UIFoundation 0x00007ff804a1e9e2 -[UINibDecoder decodeObjectForKey:] + 257 6 UIKitCore 0x000000010e566a9f -[UIView initWithCoder:] + 1327 7 UIKitCore 0x000000010e4ed417 -[UIScrollView initWithCoder:] + 65 8 UIKitCore 0x000000010e34cbd5 -[UITextView initWithCoder:] + 65 9 UIFoundation 0x00007ff804a1ecb4 UINibDecoderDecodeObjectForValue + 711 10 UIFoundation 0x00007ff804a1e9e2 -[UINibDecoder decodeObjectForKey:] + 257 11 UIKitCore 0x000000010d97e7f0 -[UIRuntimeConnection initWithCoder:] + 160 12 UIFoundation 0x00007ff804a1ecb4 UINibDecoderDecodeObjectForValue + 711 13 UIFoundation 0x00007ff804a1eebe UINibDecoderDecodeObjectForValue + 1233 14 UIFoundation 0x00007ff804a1e9e2 -[UINibDecoder decodeObjectForKey:] + 257 15 UIKitCore 0x000000010d977a79 -[NSCoder(UIIBDependencyInjectionInternal) _decodeObjectsWithSourceSegueTemplate:creator:sender:forKey:] + 447 16 UIKitCore 0x000000010d97a77e -[UINib instantiateWithOwner:options:] + 1118 17 UIKitCore 0x000000010d532dab -[UIViewController loadView] + 643 18 UIKitCore 0x000000010d533128 -[UIViewController loadViewIfRequired] + 129 19 UIKitCore 0x000000010d533960 -[UIViewController view] + 27 .... Has anyone found the solution to this issue? This is preventing us from fully validating our iPadOS 17 upgrade builds. Thanks in advance.
Posted Last updated
.
Post marked as solved
3 Replies
2.3k Views
After I've updated to Xcode 15 beta 2, I'm getting these build time errors, which I didn't see in beta 1. Failed to find or create execution context for description '<IBCocoaTouchPlatformToolDescription: 0x600002588860> System content for IBRealityIdiom-seventeenAndLater <IBScaleFactorDeviceTypeDescription: 0x600002588b60> scaleFactor=2x, renderMode.identifier=(null)'. I've tried - restarting the Xcode15 beta 2, re-installing Xcode 15 beta 2 and also its Commnad Line Tools Restarting the macOS (twice) However, nothing has worked so far. I'd appreciate any suggestions or ideas as to how to fix this issue, because I'm stuck without being able to build the projects. Thanks in advance!
Posted Last updated
.
Post not yet marked as solved
1 Replies
858 Views
Hello friends, Ever since I've upgrade to Xcode 14.3, our project has been failing to archive after build, with following error: Copy /&lt;redacted_path_to_project&gt;/Build/Intermediates/ArchiveIntermediates/LiquidDecisions/InstallationBuildProductsLocation/Applications/Decisions.app/Frameworks/LiquidPlatformKit.framework /&lt;redacted_path_to_project_root&gt;/Frameworks/LiquidPlatformKit.framework (in target '&lt;AppName' from project '&lt;AppName&gt;') error: /&lt;redacted_path_to_project_root&gt;/Frameworks/../../IntermediateBuildFilesPath/UninstalledProducts/iphoneos/LiquidPlatformKit.framework: No such file or directory (in target '&lt;AppName&gt;' from project '&lt;AppName&gt;') LiquidPlatformKit.framework is our private library/framework for our iPadOS project. I'm not sure why is this popping for Xcode 14.3+; and its the same error we're seeing in Xcode 15 beta as well. I've seen some similar issue but for CocoaPods and since our framework is not part of Pods that solution is not application to us. Have you faced similar issue? any suggestions to fix this issue? Thanks in advance.
Posted Last updated
.