Swift 6

I can confirm the same issue on iOS 26 beta 6. We have been using simultaneousGesture() as a workaround for the well-known bug, which is the same one BAR115 mentioned earlier. However, this workaround appears to be broken as well. At the moment, it seems there is no reliable way to use buttons inside sheets. This is just ridiculous.

The provisioning profile we are using is for in-house development. We understand that normally the in-house provisioning profiles expire after a year. However, after we rebuild and redistribute our app, the new in-house provisioning profile's expiration date cannot be updated. We tried to rebuild and redistribute the app in Jul 2025 and Aug 2025. The in-house provisioning profile expiration date still keeps on 6 May 2026, which is less than a year. Is there any other way to clear the cache (?) or update the expiration date of the in-house provisioning profiles?

I think this got fixed on the Xcode beta released today (6, but device version is beta 7). I say I think because it worked on my side, both 18.2 and 18.5. Very much appreciate everyone's time who addressed this.

@Bigby Woody Could you please test the code snippet I’ve provided in Xcode beta 6 and iOS 26 beta 7? I’d like to know if you’re still able to reproduce the runtime exception.

Hi! Sorry for the necromancy but this issue still persists in xcode 16.4 and xcode 26 beta 6 For now my choice of a workaround is to play with that Show live issues checkbox Such a frustrating bug for someone who tries to learn swift 🫩

@DTS Engineer Thank you so much for your reply. The issue persisted on Beta 5 so used the old-style icon export into Asset / AppIcon in place of the nice Icon Composer-made icon. But, I will test on Beta 6. If it still persists, will file a bug report. Looking forward to this being resolved in an upcoming build. Have enjoyed using Icon Composer - it makes creating wholesome icons a breeze. —Siddharth

+1 from me, also having this same issue with Xcode 26 beta 6. None of the image layers in my icon have alpha channels, but when you inspect the png produced by Xcode in the app bundle, it has an alpha channel. Logged FB: FB19782649

Update: The “You started Playing XXX” activity finally showed up after about 6 days. I’m guessing Apple’s backend needs some time to generate/review the associated data?

I’m presuming you want the resulting digital identity to be persistent, that is, to survive your app being terminated and relaunched. If so, you need to store the private key and the certificate somewhere, and the best place for storing credentials like this is the keychain. Standard practice here is: Generate the private key in the keychain. Derive the public key from the private key. Export the public key bits and send that your certificate issuing infrastructure. Get back the certificate. Add that to your keychain. Get a digital identity from the keychain. There are various APIs to support this: In step 1, use SecKeyCreateRandomKey. In step 2, use SecKeyCopyPublicKey. In step 3, use SecKeyCopyExternalRepresentation. In step 4, if the server sends you back a PEM, you’ll need to decode that to get a DER. You can then import that using SecCertificateCreateWithData. In step 5, use SecItemAdd. In step 6, use SecItemCopyMatching. We have a bunch of resources that can help with this. I recommend that you

As of now the issue still persists on iOS 26 beta 6 simulator.

Xcode 26 Beta 6 (17A5295f) appears to fix the issue at my side. 👍

This seems to be fixed with Xcode 26 beta 6. I am now able to run the iOS 17 and 18 simulators, as well as build to my device again. Excellent news! The bug reports filed by folks here were helpful in addressing this, so thank you to everyone here who took the time to file one. — Ed Ford,  DTS Engineer