Gosh, Xcode 13.3 breaks so many things...

Hopefully our friends at Apple will know that we are still waiting for a solution.

I just received a response for FB9816443 from Apple. I haven't tested it yet, but it looks like a viable solution. Add following options to “Other Swift Flags” in the build settings: -Xllvm -sil-disable-pass=alloc-stack-hoisting

Experiencing many of the same crashes on iOS 15.4. Is there any solution?

Same here. After upgrading Xcode 13.3 RC, I can't preview all my widgets. Expect a solution. Right now it's completely blocking the workflow. 😫

Same issue here. The error message "TMS-90562: Invalid Bundle" is incorrect and misleading. When you try to use Ad Hoc distribution to export an IAP, you will find real problems related to the latest SDK and Bitcode. See Unable to export for Ad Hoc or Development distribution with Xcode 13.3 RC

Exactly same issue here. Not only does it affect Ad Hoc distribution, but for normal App Store distribution, it also receives errors. "ITMS-90562: Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in dylib search path." (this is incorrect error message). Unchecking "Include Bitcode for iOS content" can workaround the problem, but this cannot be applied to apps with Apple Watch applications. Detailed error log: ipatool failed with an exception: #<CmdSpec::NonZeroExitException: $ /Applications/Xcode.app/Contents/Developer/usr/bin/python3 /Applications/Xcode.app/Contents/Developer/usr/bin/bitcode-build-tool -v -t /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin --sdk /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/SDKs/WatchOS8.5.sdk -o /var/folders/lv/58r5dhv52j779_qn41gnq4c80000gn/T/ipatool20220310-49488-1r6fqqy/thinned-out/armv7k/Payload/MyApp.app/Watch/WatchApp.app/Frameworks/libswift_Concurrency.dylib --generate-dsym /var/folders/lv/58r5dhv52j779_qn41gnq4c80000gn/T/ipatool20220310-49488-1r6fqqy/thinned-out/armv7k/Payload/MyApp.app/Watch/WatchApp.app/Frameworks/libswift_Concurrency.dylib.dSYM --strip-swift-symbols /var/folders/lv/58r5dhv52j779_qn41gnq4c80000gn/T/ipatool20220310-49488-1r6fqqy/thinned-in/armv7k/Payload/MyApp.app/Watch/WatchApp.app/Frameworks/libswift_Concurrency.dylib Status: pid 49600 exit 1 Stdout: SDK path: /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/SDKs/WatchOS8.5.sdk SDK version: 8.5 PATH: ['/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin', '/Applications/Xcode.app/Contents/Developer/usr/bin'] Using: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo MachoInfo: cd / ['/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo', '-info', '/var/folders/lv/58r5dhv52j779_qn41gnq4c80000gn/T/ipatool20220310-49488-1r6fqqy/thinned-in/armv7k/Payload/MyApp.app/Watch/WatchApp.app/Frameworks/libswift_Concurrency.dylib'] -= Output =- Non-fat file: /var/folders/lv/58r5dhv52j779_qn41gnq4c80000gn/T/ipatool20220310-49488-1r6fqqy/thinned-in/armv7k/Payload/MyApp.app/Watch/WatchApp.app/Frameworks/libswift_Concurrency.dylib is architecture: armv7k Exited with 0 Command took 0 seconds Using: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/dwarfdump GetUUID: cd / ['/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/dwarfdump', '-u', '/var/folders/lv/58r5dhv52j779_qn41gnq4c80000gn/T/ipatool20220310-49488-1r6fqqy/thinned-in/armv7k/Payload/MyApp.app/Watch/WatchApp.app/Frameworks/libswift_Concurrency.dylib'] -= Output =- UUID: 3285553C-DF9E-38CB-84BA-C5E9E898FFDF (armv7k) /var/folders/lv/58r5dhv52j779_qn41gnq4c80000gn/T/ipatool20220310-49488-1r6fqqy/thinned-in/armv7k/Payload/MyApp.app/Watch/WatchApp.app/Frameworks/libswift_Concurrency.dylib Exited with 0 ... Command took 0 seconds Found framework/dylib: /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/SDKs/WatchOS8.5.sdk/usr/lib/libobjc.A.tbd Found framework/dylib: /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/SDKs/WatchOS8.5.sdk/usr/lib/libc++.1.tbd Found framework/dylib: /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/SDKs/WatchOS8.5.sdk/usr/lib/libSystem.B.tbd Found framework/dylib: /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/SDKs/WatchOS8.5.sdk/System/Library/Frameworks/CoreFoundation.framework/CoreFoundation.tbd Search Path: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.1.6/lib/darwin, /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/watchos, /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/SDKs/WatchOS8.5.sdk/usr/lib, /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/SDKs/WatchOS8.5.sdk/System/Library/Frameworks libswiftCore.tbd not found in dylib search path Stderr: > /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:372:in `run' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:2889:in `block in CompileOrStripBitcodeInBundle' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:2828:in `each' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:2828:in `CompileOrStripBitcodeInBundle' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:2813:in `block in CompileOrStripBitcodeInBundle' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:2812:in `each' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:2812:in `CompileOrStripBitcodeInBundle' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:3115:in `block in ProcessIPA' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:3076:in `each' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:3076:in `ProcessIPA' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:4038:in `<main>'

I committed a code-level support request about this compiler bug several days ago. However, they replied that there is no workaround available, and the bug is still being investigated. Finally I realize I have to solve this apple bug by myself. Possible workarounds I found: Go back to use Xcode 13.1 Keep using Xcode 13.2 but disable compiler optimization with -Onone Write a simple container view like @available(iOS 15, *) struct Wrapper<Content: View>: View {…}. And wrap the true branch of each if-#available in ViewBuilder with it.

I opened FB9816443. I believe this issue affects all SwiftUI app that build with Xcode 13.2/13.2.1.

Same problem. Xcode 13.2 (downloaded form developer website) was fine but Xcode 13.2.1 (downloaded from app store) is no good.

I may have asked the incorrect question. TabView should NOT be placed in NavigationView because each tab needs its own instance of NavigationView to maintain independent state. This is also true in UIKit. So, the right question should be: how to implement the functionality provided by UIViewController.hidesBottomBarWhenPushed in SwiftUI?

I encountered the same problem. My Widget Extension opens a Realm database on init(). The database file located in the App Group, and later the Widget Extension receives 0xdead10cc error. I have never reproduced this problem in my own development environment, or test environment. But I can continue to collect this crash report from users. There is still no solution.

This is what I found for Catalyst mac app: If you add both CFBundleName and CFBundleDisplayName into your InfoPlist.strings file, and set "Application has localized display name" to YES in your Info.plist, then the $(PRODUCT_NAME) will never be shown to user. However, the app name is always localized to your app developent language, not to the current system language. I have not yet found a solution. In addition, the main menu and about dialog are perfectly localized. Note also that I found another serious problem with the localization of Catalyst applications: https://developer.apple.com/forums/thread/670649

Ran into the exact same problem. My app uses Simplified Chinese as the base language and also supports English. But on the Mac App Store page, it only shows that Chinese is supported. Yet when I download and install the app, it does support both languages. You can even verify the list of languages supported by the app through System Preferences -> Languages & Regions -> App. So this means there should be no problem with the app build and the problem is with the Mac App Store.

Encountered same issue on watchOS 7.2 when trying to restore a purchase using StoreKit API. Error Domain = SKErrorDomain Code = 0 "UNKNOWN_ERROR" UserInfo = { &#9;NSUnderlyingError = 0x154f34c0 { &#9;&#9;Error Domain = ASDErrorDomain Code = 500 "Unhandled exception" &#9;&#9;UserInfo = { &#9;&#9;&#9;NSLocalizedDescription = Unhandled exception, &#9;&#9;&#9;NSUnderlyingError = 0x1542a6e0 { &#9;&#9;&#9;&#9;Error Domain = AMSErrorDomain Code = 100 "Authentication Failed" &#9;&#9;&#9;&#9;UserInfo = { &#9;&#9;&#9;&#9;&#9;NSLocalizedDescription = Authentication Failed, &#9;&#9;&#9;&#9;&#9;NSUnderlyingError = 0x154a3630 { &#9;&#9;&#9;&#9;&#9;&#9;Error Domain = com.apple.accounts Code = 6 "The operation couldn’t be completed. (com.apple.accounts error 6.)" &#9;&#9;&#9;&#9;&#9;&#9;UserInfo = 0x1541d610(not displayed) &#9;&#9;&#9;&#9;&#9;}, &#9;&#9;&#9;&#9;&#9;NSLocalizedFailureReason = The verify credentials call failed. &#9;&#9;&#9;&#9;} &#9;&#9;&#9;}, &#9;&#9;&#9;NSLocalizedFailureReason = An unknown error occurred &#9;&#9;} &#9;}, &#9;NSLocalizedDescription = UNKNOWN_ERROR }