It is SO ANNOYING! I have found, however, IF I know what code I’ve added since the last successful compile, take that bit of code and move it out of your largest container. Meaning, if your entire view is I’m embed in a VStack, comment out your new code, copy it and place it above and outside the VStack, then try to build. USUALLY then, the compiler will tell you what your error is. Fix it so it compiles then move it back to where it should be. I REALLY hope the engineers at Apple will fix this though!

That is helpful, thank you, but not exactly what I was hoping for. With cmd+c, cmd+f, cmd+v I see how many matches were found and can then hit enter to cycle through them, so I was hopeful there was an existing key combination (or the ability to create one) which would mimic those 3 shortcuts but do it in one. i.e. (this is totally made up) cmd+j would magically open the find window, automatically paste the selected text in there, and perform the find for me.

Guess it doesn't matter then if it can't be done. Thanks for the reply.

We are having a similar issue. We tracked it down to when we are updating @Published vars in our view models, but have not found a work around. We are not having the app freeze, but see the CPU spiking over 100% then staying pegged at 100% until we close the app. If we run the app on a device that's at ios 17.6, no issues. Only when we run on an iOS 18 device do we see the problem.