Post

Replies

Boosts

Views

Activity

Reply to How to Fix Cracking and Popping Sound ?
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.
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’21
Reply to Combine in AppKit - issue with publisher(for: NSControl.textDidChangeNotification...
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     }
Topic: UI Frameworks SubTopic: AppKit Tags:
Apr ’21
Reply to Apple Silicon app builds but cannot launch
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?
Jul ’22
Reply to Why doesn't the Apple Vision Pro simulator appear as a run destination?
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?
Oct ’23
Reply to Xcode previews fail with JIT error
I just updated to Xcode 16 beta 3. A very simple Mac app I developed in beta 2 that previewed successfully just prior to the Xcode upgrade has started crashing on preview with the "fatalError in UVJITAgent.swift" message. It builds and runs successfully. It's only a problem previewing the app's one view.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Jul ’24
Reply to Can't install any apps on my new iPhone 16 Pro with iOS 18 from XCode
I was running into the same error with my newly acquired iPhone 16 Pro. I downloaded Xcode 16.1 beta 2 as suggested in this thread and successfully set it up for development. This morning my phone was updated to what appears to be the final iOS 18 version (as opposed to the version installed on new phones) and tried Xcode 16 (NON beta) again. This time the setup for development worked immediately. That suggests to me that Xcode 16 came with a package specifically for the final version of iOS 18, and not for the version shipped on new phones. Hopefully this will all be resolved soon between shipping phones with the latest OS version and updates to Xcode. FWIW, I updated my phone manually in Settings>General>Software Update.
Sep ’24
Reply to URL in scene openURLContexts does not exist
Thanks for pointing out my error. Unfortunately I'm still getting the same results with the correct separator: (lldb) po FileManager.default.fileExists(atPath: "/private/var/mobile/Library/Mobile Documents/") true (lldb) po FileManager.default.fileExists(atPath: "/private/var/mobile/Library/Mobile Documents/com~apple~CloudDocs") false (lldb) po FileManager.default.fileExists(atPath: url.path) false To try to determine that this wasn't just a LLDB issue, I updated my code slightly: func scene(_ scene: UIScene, openURLContexts URLContexts: Set<UIOpenURLContext>) { guard let url = URLContexts.first?.url else { os_log("URL in %@ is nil", #function) return } let fileExists = FileManager.default.fileExists(atPath: url.path) fileExists is false after AirDropping a file. And of course this is happening within the method where openURLContexts is passed as an argument, and therefore the URL should be valid. So I'm still stuck at the same place.
Topic: UI Frameworks SubTopic: UIKit Tags:
Jul ’25
Reply to Exception unarchiving UIToolbar in iOS 18.5 simulator with Xcode 26 beta 2
Like javierCantoAltomobile, I am also seeing this on device. In my case it's on an iPad running iOS 18.5. Here’s what’s logged in the Xcode 26 beta 3 console while trying to run the project (and then printing the Exception): Toolbar-Exception(907,0x1fa87db40) malloc: xxm: failed to initialize deferred reclamation buffer [2] (null) Printing description of exception->exception: Could not instantiate class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ because no class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ 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) (null) I sure hope this is fixed soon. It's a show-stopper for me on an important project. Once again, the Feedback number is FB18587743.
Topic: UI Frameworks SubTopic: UIKit Tags:
Jul ’25