It's now 2025, I'm using the latest Xcode, the latest Simulator, the latest everything. My code is not referencing NSURL (afaik) yet still... let task = URLSession.shared.dataTask(with: urlRequest) And getting a message NSURLErrorDomain Code=-1003 Have the error messages been updated?

Helllooooo??? Is anybody out there? I'm on xcode 16.3 trying to develop in Swift for minimum compatibility iOS 15, but I'm stuck setting up my development environment. Can I get some help please? All suggestions welcome.

Setting frames and bounds is no longer supported. You must use constraints. When I changed my layout to use constraints it all started working again. Another case of Apple just changing the rules. Backward compatibility is no longer a thing!

Hi Quinn Definitely an iOS app. When googling this error I came across some answers that suggested enabling the Outgoing Connections in the App sandbox. I found these settings (including an App Sandbox) in the app configuration stuff. I wasn't aware that it only applies to OSX. Cheers Murray

@DTS Engineer You have a good memory. Yes, I had similar problems with my previous MBP setup, however with your help we did manage to get it working. This time I tried over and over to drop the certificate on the simulator, and when I checked the Settings the trusted certificate appeared to be in place. However, when I tried it I continued to get this error. I might give the macOS beta a try over the weekend. Testing with a real device takes so much longer, having to commit and push code to external servers. It's a painful work around. Cheers Murray

The Sequoia beta 3 is working! And a bonus, it didn't break my local web server setup!! Thanks @DTS Engineer Please ask the developers not to break it again.

@DTS Engineer Hi Quinn Just to be super clear: As I woke up this morning I was thinking about the basics of what I was trying to do in this test. It did occur to me that perhaps the ".image" variable is private, so I made some changes to the test. As you can see, even with the public function the same error message appears. So I watched the video "What's new in Swift" and they mentioned @MainActor and this triggered my memory. So I added this before the class and voila the error went away. I'm just so confused though. "Utils" and "getImageSize" is a static function - even if called on another thread it is only operating on the object instance being passed in. I don't understand why it needs to run on the main thread??? Can you explain this please?

I watched the second video "Embracing Swift Concurrency". I'm not really embracing it yet, and the concept of Isolation is quite foreign. However, the video did make some sense. All of the UI stuff needs to use @MainActor. Swift 6.2 will make this easier as it will be a default mode. Thanks for your help Quinn. PS More questions coming...

Hi @KeithB So I have now referenced the view controller and it is working much better. Thank you for your help.