A minimal project to reproduce a UISegmentedControl tap position bug in Xcode 26.

When tapping an unselected UISegmentedControl that has dynamically set segments, the tap position is incorrectly calculated. For example, tapping the rightmost segment (index 3) results in the leftmost segment (index 0) being selected instead.

• Xcode: 26.1.1, 26.2 (confirmed)
• iOS: 18.5, 26.2
• Device: Simulator and physical devices

All of the following conditions must be met:

1. Build with Xcode 26.x
2. UIDesignRequiresCompatibility is set to YES in Info.plist
3. UISegmentedControl is laid out using Auto Layout
4. Segments are dynamically set (e.g., using insertSegment(withTitle:at:animated:) after initialization)

1. Clone this repository
2. Open SampleSelectSegmentedControl.xcodeproj in Xcode 26.x
3. Build and run on a simulator or device
4. Observe two UISegmentedControl instances:
   • Top: Standard UISegmentedControl with static segments ("Item 1", "Item 2", "Item 3")
   • Bottom: CustomSegmentedControl with dynamically set segments ("Item A", "Item B", "Item C", "Item D")
5. Tap on the rightmost segment of the bottom (custom) segmented control

The rightmost segment ("Item D", index 3) should be selected.

The leftmost segment ("Item A", index 0) is selected instead.

class CustomSegmentedControl: UISegmentedControl {

    func setSegments(titles: [String]) {
        removeAllSegments()
        titles.forEach { title in
            insertSegment(
                withTitle: title,
                at: numberOfSegments,
                animated: false
            )
        }
    }
}

class ViewController: UIViewController {

    @IBOutlet weak var topSegmentedControl: UISegmentedControl!
    @IBOutlet weak var bottomSegmentedControl: CustomSegmentedControl!

    override func viewDidLoad() {
        super.viewDidLoad()

        topSegmentedControl.selectedSegmentIndex = UISegmentedControl.noSegment

        bottomSegmentedControl.setSegments(
            titles: ["Item A", "Item B", "Item C", "Item D"]
        )
        bottomSegmentedControl.selectedSegmentIndex = UISegmentedControl.noSegment
    }
}

<key>UIDesignRequiresCompatibility</key>
<true/>

Currently investigating potential workarounds:

• Setting UIDesignRequiresCompatibility to NO (if acceptable for your app)
• Using static segments defined in Storyboard instead of dynamic insertion

For more detailed analysis: https://dev.classmethod.jp/articles/xcode26-uisegmentedcontrol-tap-position-bug/

• Apple Developer Forums: (To be added)
• Feedback Assistant: FB21712773