I'm going to link my recent response to this thread (see below):I'm working with CoreBluetooth- and can't debug over simulator. When I run a simple app that writes to a label, I see my debug statements on the console when deploying to a simulator. The minute I switch over to a real device, I can't debug and breakpoints don't even work. The funny thing is my watch os app is still updated. The real problem is how to effectively debug on Xcode when using a real device. I've updated Xcode, and all my software. I paired and unpaired my device. Downloaded the profile for watch os on my phone. Nothing is working. I'm on watch OS 6.1.1, Xcode 11.3.1. If there is some solution that I missed, I'll be happy to try. Apple doesn't cover this bug or incident on their docs or how to solve. I want to be able to see my logs, even if my app doesn't crash.EDIT: Preface, a few days ago when I was working in CoreBluetooth and building an app, the console on Xcode worked- I was able to see all my devices, debug statements, and such when I deployed to a real device. Even when not working in CoreBluetooth and just building a simple app, the debug statements worked on the console when I deployed it to a real device.Other steps I've taken:• Went to Debug --> attach process by PID (didn't work)• Windows -> Device/Simulators (can only see when something crashes on the console- but no debug statements)• Deleted derived data (edit)It's just recently, like last night, I ran into this problem. I can't find the solution or understand WHY this is happening.Reference posthttps://forums.developer.apple.com/message/403205#403205Please let me know if I need to include any other pertinent information. Thanks !!nadine