I'm running locally on my Mac on real devices (tested on iPhone 14 Pro Max and iPhone 13 Pro, both iOS 17). I also tested in a simulator and the debug works fine on "Wait for the executable to be lauched" mode. The problem only occours on attached devices.
douglasantoniaz
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Additionally, I did one more test that may be usefull to investigate the origin of the problem:
On another Mac device (Intel processor), using macOS 13.6, I installed Xcode 14.3.1 and I ran the same project on a iPhone 7 (iOS 15).
I was able to debug my app on "Wait for the executable to be lauched" mode normally.
So, according to my tests, the problem occurs in this scenario:
MacBook Pro M1 (macOS Sonoma 14.0)
Xcode 15
Any real device (tested on iPhones with iOS 17)
"Wait for the executable to be lauched" mode
I don't know if the following information is relevant, but my app has Swift and Objective-c code.
Hi,
Unfortunately I don´t have an iOS 16 device.
As requested, I created a "Hello Word" project, and the problem is still occurring, as you can see in the picture I attached in the comment below. Using simulators, the problem doesn't occur.
I have been following the case closely and I'd like to know if there is any update on this matter.