I'm very upset because I feel like it should be easier to find than this, but in the docs (and the Float16 header): /// A half-precision (16b), floating-point value type. /// /// `Float16` is available on Apple silicon, /// and unavailable on Intel when targeting macOS. sooo, basically, if you conditionally compile for arm, it should work: #if arch(arm64) @available(macOS 11.0, iOS 14.0, *) let value: Float16 = 0 #endif

It appears to be centered around the usage of a custom scheme in the HLS m3u8 file link to the encryption key: if I use http(s) to link the encryption key, it works fine. If I use something custom like fakey, it never even makes it to the delegate method for AVAssetResourceLoaderDelegate called resourceLoader(_ resourceLoader: AVAssetResourceLoader, shouldWaitForLoadingOfRequestedResource loadingRequest: AVAssetResourceLoadingRequest) where I'd swap out the scheme for a real one, because it crashes first. So far, I can only replicate this on the iOS 15 simulator. I've opened a feedback: FB9764319

Turns out I'm ****** and it's easy. Just set the value when you are configuring the cell in whatever cellForItemAt variant you are using. func configureCell(_ cell: UICollectionViewListCellSubclass, indexPath: IndexPath, item: DataSourceItem) { cell.titletext = "Cell Title" cell.subtitleText = "1/2/2021" cell.indentationLevel = 0 // or whatever }

I'll have to give that a watch when I have a moment, and I'll try to find time to isolate it for a bug report, but I'm not optimistic about that happening. Life at a startup, you know? That backlog ain't going to shorten itself. Is it worth filing a bug report without a sample project? I could at least provide some context and hopefully get it noticed.

hmm... that might help in some scenarios, but po is my real bread and butter for debugging. Is there seriously no one else experiencing this?

Was this ever resolved?

Experiencing this here in beta 6 as well. Such a crucial feature sitting this long (since beta 1 if I recall correctly) without so much as a mention does not inspire confidence. I've reported with feedback and this is the ID: FB8533272 I also attached the sysdiagnose files as was requested of the OP as well.

https://developer.apple.com/forums/thread/651533

Happening for me too on Catalina and Big Sur (Catalina, live preview and simulator, Big Sure I was only able to get the simulator to work). What's also weird is that, with the workaround from @mjfigueroa, the Add button disappears after briefly appearing.

This is definitely something that should have better documentation.

I've been helping a friend with what appears to be the same issue. He has a MBP 2018 and I believe the same versions you mentioned.We were able to test an app without frameworks in the simulator, but our app with frameworks (using carthage, but I dont think CARTHAGE is at fault).