This bug has been sticking around like a bad rash—surviving Xcode and iOS updates, version after version. The only thing that sort of works is unpairing the device, and even that’s not a real fix. What’s truly frustrating is how often it shows up. Honestly, Apple engineers shouldn’t be asking developers for logs to reproduce it—if you use Xcode regularly, you already know how common it is. Is it really that hard to make the whole “detect device, run app, launch” flow work as smoothly as it does in Android Studio?
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: