Post

Replies

Boosts

Views

Activity

Reply to Debug statements when deployed to a real device doesn't work for watch os
Update: The only real workaround is not ideal and not sustainable, but temporary fix. Write your code for iOS and debug there, and translate your app to the watch os workflow. (I'm building a watch os-only app). Apple needs to figure out why this is happening or else connected products for watchOS will be a real nightmare to make and deter anyone from pushing IoT - like apps to the Apple store.
Jan ’20
Reply to xcode 9 - all of the sudden no debug session for watch app
I'm running to the same issue. Unfortunately, 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. Paired and upaired my device. Downloaded the profile for watch os on my phone. Nothing is working. I'm on watch 0s 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.It's just recently, like last night, I ran into this problem. I can't find the solution or WHY this is happening.
Jan ’20