UPDATE: This is happening on that machine even when targeting a new phone and with a fresh install of XCode 11! It must be something hosed in the environment... What outside of xcode could be involved with this? Bear in mind that it's not broken - just takes *60 seconds* to attach the debugger.
I'm facing the same issue now. Did you resolve the issue patniemeyer?
- only on my iMac and iPhone 11pro combination, it doesn’t happen if I build on another macbook or if I try it with another phone
- for any app, even the newly create sample app
- only if “Debug executable” is turned on in edit scheme, and if I just run the app from the homescreen it’s fine
What I tried already:
- deleting derived data ofc
- restarting the phone
- restarting iMac
- reinstalling Xcode
- clearing trusted computers from the phone
Hi! I was suffering from the same problem.
My development environment is as follows.
Xcode 11.3.1, iPhone 7 iOS 13.3.1, MacBook Pro (2016) macOS Catalina version 10.15.3
I was able to solve it in the following way.
1. Quit Xcode.
2. Open the Mac desktop application Terminal.app.
3. Execute command "rm -rf ~/Library/Developer/Xcode".
4. Open Xcode.
5. Select the Xcode menu "Product - Scheme - Edit Scheme".
6. Check the "debug executable" in "Run - Info"
7. Then I was able to debug.
I encountered the same problem today.
Xcode 11.4.1, Mac mini 2018, macOS Catalina 10.15.3,
tested with two iPhone 6(both are iOS 12.4.6), they have this problem too(but not in every launch),
also tested with an iPhone 8+, which doesn't have this problem at all
I deleted folders inside ~/Library/Developer/Xcode/iOS DeviceSupport/ (folder's name started with 12.4.6), then run Xcode and launch an app again, problem solved.
What a weird bug...