xcode github

You were right. We've found out that the issue was that we registered an observer with addObserver using a #selector that pointed to a function marked as @MainActor, but we were calling the NotificationCenter.post method from a background thread. Apparently this caused the main-actor isolation check to fail, which led to a crash. Even though there is no data-race or UI operation in the function, looks like it is enough for the function to be @MainActor to cause a crash when called from outside the main thread. We fixed it by making sure the relevant NotificationCenter.post calls are executed on the main thread. Initially, we thought that marking the function with @MainActor would prevent it from being called from a nonisolated context by producing a compile-time error in Swift 6 mode. But since a Selector instance is not aware of the actor isolation of the target function, Xcode is not able to show a warning and it caused us to not realize the issue at first. I appreciate your guidance @DTS Engineer.

Thanks for the post and the description. Never seen this, so I don't think is a bug, what version of Xcode are you using? Have you updated to the latest? Could you please provide a list of the macOS, Xcode, and simulator/physical device versions? Do you get the same results with just the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.

Hi I share the code of function that launches the stream query: func lanzarPeticion() async{ defer{👎🔘lanzarConsulta.toggle()} do { let sessionStream = LanguageModelSession(model: modelStream, instructions: instructions) let genOptions = generarSamplingMode(temperatura: temperatura, maxResponseTokens: maxResponseTokens, probabilityThreshold: probabilityThreshold, topK: topK, seed: semilla) let responseStream = sessionStream.streamResponse( to: prompt, options: genOptions) for try await partial in responseStream { withAnimation{ self.respuesta = partial.content t.createPartialTime() } } withAnimation{ t.stop() } } catch { // all the logic for errors } } Clarifications about the code: First of all, English is dominant on code but sometimes use Spanish, my native language, specially when terms overlap swift or framework ones; I have my own emoji rules to avoid characters an improve readability (at this moment I'm indie developer so I set the rules) The defer block is to free the button that launches the request

Thank you! Developer feedback is vital to making Xcode even better. If you have any other feedback, please use the Feedback Assistant. You can access Feedback Assistant directly from Xcode, and use it to report issues you encounter or request enhancements to tools and services.

Thanks for the post, I am not familiar with the third party React Native. You should check with the support resources provided by the 3rd party to get assistance with their software. Unless another developer in the forums has experience with the third-party and can provide assistance. My sole recommendation is to ensure that your macOS is updated to the most recent version, as well as your Xcode. Additionally, I suggest contacting React Native support to inquire if they have encountered similar issues. Good luck. Albert Pascual
  Worldwide Developer Relations.

@Zhaocheng Please try the new Xcode that is currently in beta to see if fixes your issue. Let me know what results do you get please. Thanks @marceloamx Albert Pascual
  Worldwide Developer Relations.

Xcode Version 26.2 beta 2 (17C5038g) iOS Version 26.2 (23C5044b) do { let response = try await AgeRangeService.shared.isEligibleForAgeFeatures // Handle response if response { print(Eligible for age features) } else { print(Not eligible for age features) } } catch AgeRangeService.Error.notAvailable { print(isEligibleForAgeFeatures not available error) } catch { print(isEligibleForAgeFeatures Unhandled error: (error)) } The above code snippet gets hang at the API call isEligibleForAgeFeatures could you please suggest what is wrong here

Hello I'm wrapping my head around on how to properly set up xcode project to produce a static library Why? file locations /usr/local/lib/libXXX.a and /usr/local/include/XXX/xxx.h so it can be used Unix style in other projects That's not really the way that macOS works. I could write an old style Makefile and have xcode call the makefile but there must be an easier way to do this. What's wrong with a makefile? Xcode is designed to build iOS apps. There is no easy way to make it build open-source style archives and headers. And why should there be? Any open source project would be using standard tools to do this kind of thing. They would never, ever use Xcode. This is for a cross platform development so having it packaged into a Framework would not solve it neither. The Mac and Xcode are not useful for cross-platform development. Just use whatever standard tools fit your technical and social requirements - autotools, CMake, Google-build-engine-du-jour, whatever. Now