@DTS Engineer Hi Quinn, I double checked, in an iOS playground, this time with an older Xcode (13.2) on an older Mac. And it does work, as it did with Xcode 16.4, as shown by the screenshot.

Try to downlaod from here: https://xcodereleases.com

It happens, from time to time, but only with a few, not the full series. Try to remove all disconnect from appstore reconnect try uploading a first one. if that works, proceed with all.

What do you expect ? startAccelerometer is never called. To test, you could add a Button which action will call startAccelerometer().

Did you try removing the transparent effect and see if the systems does it by itself ? Do you upload to AppstoreConnect from Xcode 26ß ?

It works in iOS playground, but not in MacOS playground, either Xcode 16.4 or 26.0ß6. So, that's definitely a bug you should report. You got the answer in your SO post: https://forums.swift.org/t/why-is-there-a-type-of-expression-is-ambiguous-without-a-type-annotation-error-when-using-a-ternary-operator-on-inferred-function-types-in-swift/77306/2 As said, this works: func chooseStepFunction(backward: Bool) -> (Int) -> Int { let res = oneStepBackward ? stepBackward : oneStepForward return res }

This is a question on the use of device, not a question about app development. So you should ask on the community forum (https://discussions.apple.com/welcome), or file a bug report.

Just linking to another forum is not the proper way to use the forum. Please read this excellent thread on how to properly use the forum: https://developer.apple.com/forums/thread/706527

Which Xcode version do you test with ? Do you test in playground or in app, or SwiftUI App ? I tested in Xcode 16.4, with the following call: print(chooseStepFunction(backward: true) (10)) And got 9 as expected. I tested also in Xcode 26 ß6, works as expected. How do you use chooseStepFunction? please give more context.

So the question is: did the required signature for selector change in Xcode 26 ? I have noticed the same issue for other types of control.

I have not found a way to do this with existing API. Probably because it would break from liquid glass look and feel (which would be an issue for UI consistency). Looks like one need to create custom segmented control. I've found a lot of information here: https://focuspasta.substack.com/p/building-a-custom-segmented-control

That's at least a documentation bug (or an error compiler should detect). I note the modified code also works with Xcode 16.4 / iOS 18.4, but givesa different UIControlEvents value Slider value changed to: 0.00042842288 UIControlEvents(rawValue: 105553178306624) Slider value changed to: 0.0038560412 UIControlEvents(rawValue: 105553178306624) So, yes, I think it is worth a bug report, because many of us will face the issue. Let's wait for DTS engineer analysis, in case. Then close the thread.

Effectively, your code crashes in Xcode 26 / iOS 26 (but works in Xcode 16.4 / iOS 18.4). I think problem is the type used for event. I changed UIEvent in sliderValueDidChange: @objc func sliderValueDidChange(_ sender: UISlider, for event: UIEvent) { to UIControl.Event @objc func sliderValueDidChange(_ sender: UISlider, for event: UIControl.Event) { print("Slider value changed to: \(sender.value) ") print(event) } No more crash, just the log: Slider value changed to: 0.025641026 UIControlEvents(rawValue: 0) Slider value changed to: 0.03926282 UIControlEvents(rawValue: 0) Did Xcode 26 replaced UIEvent by UIControl.Event ? In that case I could not find it in documentation.

If it waits for review, that means it is an automatic process, not a reviewer's. Did you have any review incident in the past ? Maybe some background check with your account ?

My understanding was that OSs renaming was to align all the OS versions, and no more WatchOS 10, iOS 17, MacOS 15, TVOS 18, VisionOS 2… But there is no such need for the devices themselves. In addition, their update cycles are different, so that would be hard to manage.