UISegmentedControl Not Switching Segments on iOS Beta 26

While testing my application on iOS beta 26, I am experiencing issues with the native UISegmentedControl component from UIKit. After implementing the control, I noticed that I am unable to switch to the second segment option—the selection remains fixed on the first segment regardless of user interaction. I have already reviewed the initial configuration of the control, the addition of the segments, and the implementation of the target-action, but the issue persists. I would like to understand what could be causing this behavior and if there are any specific adjustments or workarounds for iOS 26.

I created a minimal application containing only a UISegmentedControl to clearly demonstrate the issue.

ive run into this same issue i think its an actual issue with the segment control in interface builder, ive submitted a feedback but you should as well! If you create the segmented control programmatically it functions fine.

I encountered the same issue with a UISegmentedControl in IB using Xcode 26 beta 1, but this is mostly fixed in a simple test app I created when using Xcode 26 beta 2. The first tap on an unselected segment has no effect, but thereafter the control works. However, the title of the manually selected segment is still obscured as it was with Xcode 26 beta 1.

Please file a bug report and post the Feedback ID here once you do. I'll also suggest you test on the latest build as well.

Bug Reporting: How and Why? has tips on creating your bug report.

Here's the Feedback ID for my bug report: FB18376874. Thanks.

My Feedback for my bug report: FB18370318 (Create UISegmentedControl from interface builder does not work well). Thank you.

Do you observe this issue on a real iPhone running iOS 26 beta?

On simulators running iOS 26 beta or iPadOS 26 beta (under Xcode 26 beta 1-3), I observe the two following issues:

  1. When the first segment is selected and I select interactively a segment other than the first segment, the newly selected segment is hidden behind an opaque selection marker. This resembles the OPs observation in this thread numbered 789898.
  2. When another segment than the first is selected and I select interactively another segment than the first, the first segment is selected instead. This corresponds to an issue reported in another thread numbered 791988.

On a real device, however, the segmented control works as expected. I have tested this with the same code on an iPad Air 13" M2 running iPadOS 26 beta 3 (and with the previous betas). The segmented control also works correctly even on simulators when I select the segment programmatically.

I currently cannot install iOS 26 beta on a real iPhone device to test this issue. Can anybody test UISegmentedControl on a real iPhone running iOS 26 beta, and thus verify if this is just a simulator issue?

Feedback submitted for unreadable segment https://feedbackassistant.apple.com/feedback/18931349

Feedback submitted for only first segment being selected https://feedbackassistant.apple.com/feedback/18931336

My bugreport FB18336315 does include a test project. The bug is still present in iPadOS 26 Beta 4

Tested on the latest iOS 26 Beta 4 simulator and the issue is still visible. I have submitted a bug report (https://feedbackassistant.apple.com/feedback/19015834).

bumping this, still an issue with Interface builder segmented controls in beta 4, I would prefer not to rewrite all my views to programmatically add a segmented control :)

I'm experiencing all the above issues with beta 4. And now a new issue where segment text/images are not properly aligned vertically. Here's an example...

Feedback: FB18304238. I have this problem as well specifically on a phone. I've subclassed UISegmentedController to be a deselectable segmented controller - I want the segment to turn off if the user taps the selected control. This works great on iOS 18-. On 26, I captured the touches ended, and rather than the proper segment for the geometry, (i.e touch at x310/320 should be index 2), it returns a sometimes random but mostly segment 0 as the selected index, rather than what the touches are reporting. My feedback has this log as well as a movie of the behavior.

The selected segment also doesn't use our custom font and color, and instead just draws black.

this looks to be fixed in beta 5! dont have xcode beta 5 yet to confirm that apps built against beta 5 look good, but apps built against beta 4 running on a device on beta 5 work as expected

Confirmed both these issues (unreadable segment, first segment always selected) are fixed in beta 5, installed from Xcode beta 5. Good job Apple!

UISegmentedControl Not Switching Segments on iOS Beta 26
 
 
Q