Thanks for the fast response.

Update: I fixed it by creating another simulator device.

Thanks. I have submitted feedback with ID: FB15362166

@edorphy Thanks for the feedback. I got it working in the end by using Swift instead of Objective C. I am not querying anything but instead setting it using the workout object that is returned when finishing the live workout. That seems to work fine, although it can sometimes take a while to get from the watch to the Fitness app on the iPhone.

I'm not the OP so I don't think I can do that, but thanks again for your help.

I also developed a workaround. This involved the watch app sending a message to the iPhone app when it received the file. The iPhone app would then handle the message in the same way that it handled the didFinishFileTransfer callback. It's not ideal but worked for my use case.

Unfortunately it has not been fixed in iOS 17.5.1

That's great to hear! Thanks for that. I will let you know if there are still problems.

Unfortunately not. As a workaround I am using GPS (outdoors) or laps and pool length (indoors) to determine the distance. Unfortunately this means that the distance shown in the app is often different to that eventually shown in Apple's apps.

Almost 6 years later I am getting the same problem when using SceneKit in SwiftUI. It looks fine in the simulator but washed out on the device. I tried disabling the linear color space in both the watch extension and the watch app but neither have helped. Is there a different way that I can disable it which would work with SwiftUI? Thanks in advance.

Many thanks for looking into this. I have submitted FB11755930 I managed to reproduce it with a Swift only project that was created by adding the intents files to the sample workout project from WWDC 21. I have attached that project to the feedback, as well as the sysdiagnose files. Please let me know if you need any more information.

Any news on when the documentation will be available? I managed to get something working from unofficial blogs and tweets, but that has been broken in watchOS 9.1 for some users. Also, the action button doesn't seem to be detected when a workout is paused (unless it was paused by the button). And is there a way to detect when both the action button and the side button are pressed at once? This is supposed to act like a pause but seems to do the same as pressing the action button alone.

Not yet. I am still hoping that the documentation will help when it is published.