This is awful. What was once called up an agent with one click without changing your visible editor files has become a kludgy mess. Who approved this and do they still have their job?

Thank you Albert. I tried foregroundStyle primary and systemBackground but the dots remain invisible on the confirm password field after autofill. I discovered that textFieldDidChangeSelection only fires on whichever field has focus when the password is suggested. The confirm field gets filled silently with no delegate callback or SwiftUI state change, so I have no hook to trigger the color re-apply. How would you suggest forcing the color update on a field that receives autofill without focus?

My bad, it returned "Cannot find 'SFSpeechLanguage' in scope" But even worse, also my bad, it turns out that I should have been using SFSpeechLanguageModel I really wish this forum would allow you to delete your OP.

Sorry, but I have to turn off WiFi on my iPhone to get the debugger to work over the wire (speed tells the truth).

What I realized, just now, is that it only works from my Mac's internal HD, the boot drive. When I tried it off of my external HDs, which is what I do all of my work from, I get the message: Simulator device failed to open file:///Volumes/Ext.%20Micron%20SSD/sergioq/Documents/myfriend.html. Somehow I never stopped to realize to try the boot drive. Thanks

hopefully it’s this: FB13788117

I accept your answer, but that shouldn't be the answer. As dangerous as certain things are, i.e. calling a null pointer, we should be allowed to design as we like.

Finally happened again, so I ran sysdiagnose before and after and submitted it to feedback

That's what I was looking for. Have been trying to find a website that lists all modifiers that Apple provides.

I assume because the other published vars aren't affected, that it has to do with the fact that the NavigationView is wrapped in an .alert(item: ) might have something to do with this warning and supposed solution? Won't mark this solved, will wait for some more input from other developers, as I am too green.

I really like Ray's (Wenderlich) tutorials.

It was just a simple oversight, because I was trying it out quickly. It’s now in there and cell is no longer an optional.

I find the way Swift handles certain things (i.e. the OP) a little too drawn out. Therefore I doubly appreciate this excellent, well explained answer.

I have to clean them up, because at first I was using the wrong delegate. However, I do need to eventually add download as well. So will have to see which I need and don't at some point

I currently have it as below, so that the completionHandler gets called first and no matter what ` func urlSession(_ session: URLSession, dataTask: URLSessionDataTask, didReceive response: URLResponse, completionHandler: (URLSession.ResponseDisposition) -> Void) { completionHandler(URLSession.ResponseDisposition.allow) if let httpResponse = response as? HTTPURLResponse { xFile?.httpResponse = httpResponse.statusCode DispatchQueue.main.async { [self] in if httpResponse.statusCode != 200 { ...my code } } } }`