Same issue here... I really hope they will find a solution otherwise the banking app where I'm working on will have some serious problems... The textfiled does not become firstResponder.

I may have find a workaround to this issue... not a solution but a workaround. I have to work on a not really recent project that was built using the Legacy System that, as you may know, is deprecated now. While I was using Xcode 12 everything was fine. Then I installed the Xcode 13 GM and I upgrated the project to the new building system and I started to experience this issue. I have the same problem with any Xcode 13.x version. With the betas I had not, as far as I can remember. The strange thing is that "sometimes" (I could not reproduce it sorry), the new build system worked... but just for a while. The building phase succeeds but then, then the app is installed on simulator OR on a real device, I have that annoying message that we know... This morning I may have find a solution... In Xcode go to File -> Workspace Settings, keep the Legacy Build System and check the box "Do not show a diagnostic issue about build system deprecation" Now the app builds and can be installed. Honestly I don't know it is an Xcode bug or not... maybe it is.

I'm experiencing the same issue, I think. I'm testing with a simple app with a simple fullscreen map... If I launch the app on my iPhone connected by cable with my Mac everything is ok. If I launch it "disconnected" I have this crash. libc++abi: terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument dyld4 config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Developer/usr/lib/libBacktraceRecording.dylib:/Developer/usr/lib/libMainThreadChecker.dylib:/Developer/Library/PrivateFrameworks/DTDDISupport.framework/libViewDebuggerSupport.dylib terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument Full crash