Same here. It seems to occur if I use import Playgrounds and the #Playground macro in a SPM module. So far I haven't found a workaround. Just don't use the playground macro. (Side note: Why do I feel that it happens all the time that features are made for WWDC presentations, but do not work at all in reality, and fail in the most basic setups? I came to the platform, because it didn't use to be that way…)

I realized that if I delete all code except for one Preview, it still does not work. If I then remove all SPM dependencies, the Preview works. It doesn't work if there's even one dependency, no matter which one. Hope that helps in finding the issue.

Filed feedback with diagnostic information as FB14728865

Got the same issue in Xcode 16 Seed 5 (16A5221g)

In the CarPlay video they talk about SF being a variable font, that can adjust boldness, italics, roundedness etc with arbritary values. I did not research how deep you have to go down in the font system, but that seems to be the way to do this. Those glyphs are not a special font, but a different set of those variable parameters.

Got the same. Everything seems to work fine though, but the warning has been there for a few betas already…

In the hideFlux function you are creating a new instance of your HostingViewController that is different from the instance you are presenting, so calling dismiss on it does nothing. Call dismiss() on the presentedViewController, which should be the ViewController you instantiated in the showFlux method. In general though this is a very brittle pattern. Your code should call the dismiss function from within the ViewController that is to be dismissed, so there is no ambiguity on what should be dismissed. Also, this is basically UIKit code, if you want to do it in SwiftUI, it is all a bit different, and maybe you shouldn't need to get down to the UIKit layer in the first place.

I found the answer: Delete ~/Library/Developer/Xcode/iOS\ DeviceSupport, restart Xcode and let it re-build the Device support. Afterwards the app starts with the debugger attached as quickly as before.

Specifically, a ResolvedSymbolConfiguration that can resolve in a Canvas would be the thing I look for. This should have getters for scale, pointSize and weight.

HomeKit already supports Thread based devices that work with the HAP protocol in iOS 14. Matter works on top of Thread or Wifi (with some BLE for discovery…) and if I see this correctly, the examples they provide are based on Matter with Thread. While Matter devices will appear in HomeKit, they said in the session that you can control Matter directly without HomeKit, too. You have to install a profile for the Matter support, as it's a "Developer Preview", which kinda means it's even more beta than the beta ;-) Also everything "Matter" is called "CHIP" in the current build, because that's the "old" name.