Post

Replies

Boosts

Views

Activity

Xcode 13.3 Not Linking Storyboards
I have a project that builds and runs with no issues when using Xcode 13.0. However, if I close 13.0, and try to then build and run the project using Xcode 13.3, the app will build, but then crash immediately on launch with the following error: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Could not find a storyboard named 'Main' in bundle NSBundle I'm making no changes in the project at all - the only change being the version of Xcode used to build the app. When comparing the build output between the two versions of Xcode, I have noticed that 13.3 is skipping the "Link Storyboards" step. A few things that I've tried include: Removing the storyboard file from the .xcodeproj, and re-adding it. Removing all localization from the project, thinking it may be related to that. I then tried re-enabling localization. Creating a brand-new storyboard using the File > New> File… menu. Even the new .storyboard files are not linked or added to the project. Removing and then re-adding the .storyboard files to the Copy Bundle Resources build phase. Bumped the minimum deployment target from iOS 13.0 to 14.0 Cloned my source code from Git to a new location and built from there. Product > Clean Build Folder and manually deleted the derived data folder locations more times than I can count. I'm using the default Derived Data location. (~/Library/Developer/Xcode/DerivedData) I've been able to verify that the storyboard files are not being included in the finished app by inspecting the .app bundle after the build succeeds. All other resources I've been copying to the app are there, but the storyboards are not. Has anyone else seen this issue, and if so, resolved it? I've been stumped for a few days now, and so far, the only thing that's worked has been rolling back to Xcode 13.0.
1
0
913
Apr ’22
Xcode fails to add any product to Xcode Cloud
When trying to create a new workflow for a framework product, Xcode fails, displaying the error: “MyFramework” could not be added to Xcode Cloud.” This framework previously had a workflow running on Xcode Cloud, but it is no longer visible, both in Xcode and App Store Connect. I was trying to recreate the workflow, as well as setup some additional ones, but I get the same error for every single product. No other details are provided by Xcode, so I’m unable to determine what steps I should take to correct the issue. I'm able to reproduce this with every xcworkspace file I have tried so far. Using Xcode 13.1 (13A1030d) It would be great if Xcode could provide some sort of detail with these error messages so that devs would know whether there is something wrong on the Cloud side, or if it's something that I can try fixing on my side.
1
1
1.7k
Nov ’21