I tried this on a test project on Xcode 14.2 (14C28) on Ventura 13.1. It gave me multiple build errors. And this was a SwiftUI project that I created. Looks like the errors are basically saying I can’t have two Info.plist files. Another note, my Xcode was auto updated to the 14.2 built (pointed out above) two days ago!! Rather suspicious to me!!!

Thanks. That worked for me!!

I did read the above docunetaditon. However, there is no explanation as to why a Folder is now being created instead of a Group at initial project build. A folder would be fine if I could manage the position of the files within in. It appears that all I get is alphabetical order. So what I need is the initial project build to create a group linked to a "real" folder at initial project build. Otherwise, I must covert the folder to a group to get the same file management behavior as in xcode 15.

I am seeing this issue on a Macbook Pro M3 max running Sequoia 15.0 RC. I submitted feedback FB15087187.

I'm still having the issue on a Macbook Pro M3 Max at 6:45pm CDT on 9/10. I submitted a report in Feedback yesterday: FB15087187

I'm still having the issue at 6:45pm on 9/10. Running a Macbook Pro M3 Max. macos is 15.0 RC, Xcode version is 16.0 RC. The mac has 1TB storage. I submitted a Feedback report last night. ID: FB15087187.

Still doing it with xcode 16 (16A242d). If I turn of parrallization off by gping to: Edit Scheme -> Test -> -> Options... and uncheck "Execute in parallel (if possible) it works. It just open the actual simulator.

As you suggested, I upgraded my Sequoia 15.0 RC to Sequoia 15.0 found in the Apple Store. FYI, the build numbers for the RC and the Apple download turned out to be the same (24A335). I first switched off Beta Updates in Automatic Download options. After the "reinstall of 15.0", I turned beta downloads back on and Sequoia 15.1 Beta 4 was again offered for install. I was able to install with no problems. Using a MacBook Pro M3 Max.

So are you saying the fix for this issue is to setup the Charles Proxy on our iOS xCode simulators to "fix" this issue with 18.4 simulators? I would hope that this would be a very short term solution!!

Ok got it. Thanks!!

It would be nice if AsyncImage did offer that level of customization!! I went ahead, bit the bullet, and created my own custom replacement for AsyncImage that really works better for my use case (displaying images retrieved form Urls in a list view). It uses NSCache to cache the images after initial download. It works great on 18.4 simulators when I set the URLSession configuration to URLSession(configuration: .ephemeral). It's based on a couple of posts I found on Google.