Both issues seem to be gone in iOS 26.0 beta 6

@lmDeveloper1 Confirmed, both issues are gone in iOS 26.0 beta 6

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: 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 issue discussed in another thread numbered 789898. 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 the OPs observation in this 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?

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: 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. 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?

Has this bug ever been fixed, or have you ever found a workaround for it? I have got this behavior in iOS 18.1. I did not notice it in iOS 18.0 or 18.0.1 or the later betas. Could it have reappeared with 18.1?

Thanks, the UIKit answer is that UITabBarController.mode can be set to UITabBarControllerModeTabSidebar. It only adds a sidebar icon that can open a sidebar with the icons. That does not help, it only makes the UI clunkier. The suggestion feedback is at FB14536289.

Disclaimer: I am not a lawyer, and none of the text below should be regard as legal advice. In my reading of the official and final text, traders that qualify as micro- and small-sized companies are exempted from having their detailed contact data published on the platform. The Contact Information Verification form on App Store Connect does not provide an option for a self-declaration as a micro- or small-sized company. Instead, it cannot be completed without filling the e-mail and phone number fields. This form states that this information will appear on the App Store in certain countries or regions. This form therefore violates the DSA, and Apple should amend it.

The issue seems to be fixed on the released versions of iOS 16.1 and iPadOS 16.1.

A study from Mark Strit et al. from Bordeaux University in France indicates it might be possible. Unfortunately this forum does not let me include a direct link to it.

@darkpaw Absolutely, here are my device screenshots. I don't known why the forum refused to include them in my original post earlier this week. iPadOS 15.7 systemSmall widget: iOS 16.0.2 systemSmall widget: iOS 16.0.2 accessoryRectangular widget:

The timer counts in a .accessoryInline widget but not in .systemSmall, .accessoryCircular, or .accessoryRectangular widgets.

Hi corin, some of my users reported frequent disconnection issues in multipeer connectivity. I could reproduce them only in situations when switching off WiFi forces MCSession to use Bluetooth. Does that match your observations? Have you found another workaround or even the root cause in the meantime?

More precisely, Xcode 12.1 can install to iOS 14.2 only after you fix it with elements from Xcode 12.2 beta 4. You are absolutely right, robnotyou, betas should not be needed to install to the latest OS release with the latest tool release. iOS 14.2 has been released prematurely.

Here is my solution: Install the Xcode 12.2 release candidate. Don't worry about renaming as suggested by CrudeByte - https://developer.apple.com/forums/thread/665891?answerId=645676022#645676022, it will install as Xcode-beta.app in parallel to your Xcode.app. It will install "additional components", though. Remove the contents of ~/Library/Developer/Xcode/iOS DeviceSupport (or at least the folders starting with 14.2) Build and run your app in Xcode-beta (12.2 beta 4, also known as release candidate). This might take a few minutes as Xcode copies caches from your 14.2 device to the device support folder You may want to continue in Xcode-beta or return to Xcode 12.1. Either will now build, run, and debug your app in reasonable time. I understand your concerns about installing a beta, as I did have issues with switching back and forth between beta and release versions of Xcode a few times in the past. This time around it seems to work. I would still not recommend to run them at the same time. tundaware - https://developer.apple.com/forums/thread/651012?answerId=616750022#616750022's answer on another thread inspired this. If you don't want to install a beta but can stomach replacing parts of your Xcode installation with material downloaded from GitHub, aaronsarkissian - https://developer.apple.com/forums/thread/665891?answerId=645879022#645879022's answer should help as well, at it is based on the same idea.

After many tries going back and forth between Xcode 12.1 and Xcode 12.2 beta 4 (the Release Candidate), I got both now to install and launch my app. However, it then gets stuck at the launch screen. The app does not start running, no debugging session is started, the console stays empty. The app does get installed. When I stop the session, I can actually run the app stand-alone on the 14.2 device. No iOS betas seem to be available at this time, and going back to 14.1 is not allowed. Questions: Is there any version of Xcode that can debug apps on iOS 14.2 devices? Do I need to stop development until Apple deigns to release Xcode 12.2?