Posts

Post not yet marked as solved
7 Replies
I'm experiencing the same problem. I just installed the visionOS 1 beta 4 via the Terminal (using the "xcrun simctl runtime add " command). That resulted in the visionOS 1.0 Simulator appearing in the list of available platforms in Xcode 15's Settings window. But when I try to add a new target to an existing project, or even create a new project, there is no visionOS option in the template chooser that appears. I have quit and relaunched Xcode a few times, but that has not helped. Is there something else I need to be doing?
Post not yet marked as solved
13 Replies
I am running into the same problem with running an iPad app on my M1 MBP. I am seeing the same error message in both Xcode 13.x and Xcode 14 beta 3. I have tried deleting the built product and rerunning the project. I have tried switching from automatic codesigning to manually codesigning the project. I have tried changing the bundle identifier with both automatic and manual codesigning. I have even tried running it after removing the one library it uses (a Swift package). None of these actions has resolved the problem. This is very frustrating because I know the project ran as a Mac app successfully last time I tried a month ago. Has anybody come up with any further solutions to this problem that haven't yet been mentioned in this thread?
Post not yet marked as solved
1 Replies
I've been seeing this message frequently today while checking out an Apple sample app running in iOS 12.4 iPad simulators. The only way I found to resolve it was to quit the simulator app and run the project from Xcode again.
Post marked as solved
1 Replies
I finally realized that I simply needed to keep a strong reference to sub. The finished code now looks something like:     private var searchTextObserver: AnyCancellable!     private var item: ModelItem!     private func setupTextObserver() {       let sub = NotificationCenter.default         .publisher(for: NSControl.textDidChangeNotification, object: searchTermText)         .map( { ($0.object as! NSTextField).stringValue } )         .debounce(for: .milliseconds(500), scheduler: RunLoop.main)         .sink(receiveValue: { [weak self] in             self?.item.value = $0         })         searchTextObserver = sub     }
Post not yet marked as solved
363 Replies
I'm having the same problem running Xcode 12.3 in Mac OS 11.1 on a 16" MacBook Pro (late 2019). After running a SwiftUI preview, or running an app in an iOS simulator, audio from other apps plays with a horrible stutter. For example, the audio track of a YouTube video playing through Safari, or a song playing in Apple Music. Whether it's going directly through the Mac speakers or through the headphone jack to my external speakers, the sound is unlistenable. I have tried suggestions I've seen online to change the Simulator's audio input and output settings in the I/O menu, and I've tried killing CoreAudio. None of these suggestions has fixed the problem. It obviously makes one's workflow much more difficult if you're trying to follow along with a tutorial video, something I've found myself needing to do a lot to learn SwiftUI development.
Post marked as solved
3 Replies
I was running into the same issue and really appreciate this solution. For what it's worth, I found that I also needed to remove the PDFKit framework that I had originally added to the project in Mojave (and that also worked in Catalina). It was causing a code signing error.
Post not yet marked as solved
9 Replies
I'm having a similar experience in Xcode 11.1/Mac OS 10.14.6. All of a sudden, trying to open storyboards in iOS projects is resulting in Xcode crashing. Trying to run these projects results in a runtime error:Command CompileStoryboard failed with a nonzero exit codeI can successfully open the storyboards as "Source". While this has affected both one of my own iOS projects, and an Apple Example app I freshlly de-archived, I am not running into this issue in a couple of Mac apps I've been working on lately.
Post marked as solved
2 Replies
I figured out the problem. I had neglected to mark my dynamic properties with the "@objc" declaration. Once I did that, the crashing stopped.
Post marked as solved
2 Replies
I just installed the GM version of Xcode 11 and I'm still seeing this crashing behavior in my example app. Is there something wrong with my setup that would explain this?
Post not yet marked as solved
6 Replies
I'm also seeing the Xcode 11 beta 7 show up as beta 6 in the About Xcode box: Version 11.0 beta 6 (11M392r)The date on the xip file in the Finder is "yesterday" which would be August 27.The date on the expanded app bundle in the Finder is "Thursday, August 22, 2019 at 2:49 PM". I believe that's the same day beta 6 was released if I remember correctly. Did the wrong version get compressed and distributed?