Here's an example: precipitation: , precipitationChance: 0.0, precipitationAmount: 0.0 mm, snowfallAmount: 3.1868364810943604 mm I can't post the full WeatherKit output for the hour because it's getting flagged for sensitive language!?

FYI, the amounts reported for the snowfall event in the USA this week were much more reasonable and close to what actually happened. The issue might have been addressed.

I'm wondering the same thing myself. I have two ForEach inside of a ViewThatFits and the code is working great when I build it locally. However, when I made a TestFlight build it was an instant crash at launch on the very same device. The crash report says that it is SizeFittingState.applyChildren(selectLast:to:) that had the problem.

No response to this one so I filed FB16418331.

I got feedback in a WWDC25 accessibility lab that a link was being read by VoiceOver as both a link and a button. I was surprised to discover that this seems to be the the default behavior. I'm also wondering if this is intentional or a bug.

This started happening for me yesterday and I still can't get in. I just filed FB20871687.

I'm back in also! Closing my ticket.

Thanks for the reply and sorry for the delay. That’s correct, these are all images that were created with Image Playground but Image Playground is out of the picture as far as this issue is concerned. When Image Playground returns the image we get back a temp URL. From that I grab the filename: tmpURL.lastPathComponent Then I get the Docs dir and move the image there. guard let documentsDirectory = globalFileManager.urls(for: .documentDirectory, in: .userDomainMask).first else { let destinationURL = documentsDirectory.appendingPathComponent(filename) try globalFileManager.moveItem(at: tmpURL, to: destinationURL) I save the new URL and use it to load the image when needed. I’ve still got all the URLs (and the VoiceOver descriptions that were added to any images) but the files themselves aren’t found any more. That does correspond to me not seeing them when I look at the app’s container. Although I do see the single test image I created after I noticed this problem.