Swift 6

I can't speak to urgency, because that could be interpreted as a future looking timeframe. As a process, I would enable the Swift 5 stricter concurrency checking in code that you control to gauge what the important issues in your code base are, and decide what it would mean to fix them in terms of complexity. After that, try out the Swift 6 language mode, and see what other issues the complier identifies, once again with an eye for complexity. You can then take that information about the technical complexity and use that as information in your overall scheduling and mangement of your software project, and when the best time to do the work is. Since you can do that on a module-by-module basis, there's no need to jump to Swift 6 all at once. You can turn it on just for one module where perhaps there are no issues, or they are easy to address, after updating the language mode, and expand outward from there. And looking at this from the other direction, if there's a module where the iss

Anybody have any idea how to use the UISliderTrackConfiguration API from Objective-C? The docs are all for Swift.

Thank you for the detailed reply. I've submitted a bug report as requested: FB19421676 – Perfect, thank you. It turns out that isVoiceProcessingInputMuted was set to true when starting a transmission, and only reverted to false once audio output stopped. This was the source of the delay between initiating transmission and receiving valid microphone input. Good find! I'm still relatively new to Swift and iOS audio development, and I was wondering if there are any sample projects or best practices that demonstrate integrating audio with the Push-to-Talk framework. No, there isn't any direct sample for it. Practically speaking, the PushToTalk framework was actually created to support an existing set of developers who'd previously built PTT apps using the voip background category and CallKit, so that they could migrate away from the unrestricted PTT entitlement. That's why we didn't create a sample— most of the framework's adopters were integrating the sample into an existing large-scale project, where a

Hello @Tinn_Vision , thank you for your question! The error you are seeing is caused by the type of property you are attempting to observe. An Entity's position is represented by the type SIMD3 , while its orientation is represented by the type simd_quatf. For SIMD3, x is a stored property, while for simd_quatf, angle is a computed property. This means the slider would have no way of setting the value of angle when a person slides the handle. For this reason, I would consider the error you are seeing to be expected behavior. You can review the Swift documentation for properties for more information. simd_quatf is a Quaternion, and while the implementation details are complex, it does not store values like the number of degrees the entity has rotated around an axis. If you'd like to make a slider that spins an entity around the Y axis, for example, you'd need to store that observed slider value someplace else, and then convert that value to a rotation, depending on what you need for your app. I'd be h

Looks like this got fixed in seed 6. Thank you!

In the meantime, I have installed macOS 26 beta 6 and the icon is back! Excellent, glad to hear the fix (r.155484172) worked! __ Kevin Elliott DTS Engineer, CoreOS/Hardware

@Ed Ford, for this useful clarification. So that means there is no urgency to switch to Swift 6 mode, unless of course there are concurrency issues or we need specific Swift 6 feature ? I understand however that it is wise to set concurrency checking at the max level, even in Swift 5 mode. Is it correct ?

Thanks. So it sounds like the NSImage is getting over-released or being incorrectly deallocated, although it's unclear to me what exactly is trying to form a weak reference, since my code (as shown above) has a strong reference. Unfortunately the higher up function calls are made by AppKit, which is not open source, so I cannot look it up. As far as I understand, the link you posted helps investigating memory issues in Xcode, but since the crash reports are downloaded by Xcode from other users and I cannot reproduce it myself... The Xcode statistics seem to show that it only happens with macOS 15.3 or newer. I don't know if it's because there's not enough space to show older releases, or if it's really a clue that it's a change introduced with macOS 15.3 that causes this issue. From my perspective it would make sense that it's a new issue with macOS 15.3, because I haven't changed the code that generates or assigns that image in a very long time, and this issue didn't happen for a previous version of my app t

Fixed in iOS 26 beta 6

[quote='853068022, Claude31, /thread/796278?answerId=853068022#853068022, /profile/Claude31'] Converting to Swift 6 is definitely not an easy ride… [/quote] Well, we’re actively working to improve that. Speaking of that, what version of Xcode are you testing this on? I want to play around with some specific scenarios and it’d be good to know whether you’re testing on Xcode 16.4 or the latest Xcode 26.0 beta. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com