Apps WorkOutDoors: New workout features

[cfc]

BETA FEEDBACK

I'm on Apple Watch Ultra watchOS 10 Beta and testing WOD 5.0. When I go into Workout History I cannot go back to the main menu. I'm stuck looking at a list of workouts and cannot use the app until I force quit the app. This issue was still present after a reboot.

EDIT: I just saw in an older post that you aren't looking into watchOS 10 beta issues. Sorry about that. If I'd realized this version of WOD was coming I wouldn't have installed the beta!

Thanks - I have seen that problem with the workout history on the watchOS 10 beta.

I will probably start looking at the watchOS 10 beta after the next beta release of WOD. Now that Apple are on beta 4 it should be getting pretty stable.

 

[cfc]

On the subject of WOD5 and WOS10, we've mentioned previously that there are long delays (lag) ending workouts and navigating some menus. I think this is related in some way to code changes around AOD. With the lag, you have to wait a while or you could switch apps and back to WOD, but actually if you lower your wrist and cover the screen, then immediately raise your wrist it speeds through the menu. The lag a few have noticed may be the screen timeout (15 or 70 seconds). Will test more after my next workout.

Sorry for the overload of TLAs, but thought I would just mention this.

Thanks for the information. It is a strange issue. Hopefully I can find some way around it when I look at the watchOS 10 beta issues.

 

[BrianGGG]

BETA Feedback

Sorry, I have a weird one that I doubt I'll be able to reproduce.
I think the sequence is:

I did an Outdoor Walk
A few minutes into it, I wanted to know what time it was
I am old and can't see the small print above, so I exited out to the main screen
I double-clicked the crown to go back to WOD
When I came back, the workout time kept working as normal, but the mileage was stuck and did not move again
When I finished my walk, I long pressed and hit END.
Rather than go to the completed screen, WOD completely stopped and my walk was not recorded in WOD history or in Apple Health

Very strange indeed, and I have only seen this once. I am very glad that it was a walk that was forgotten, not a challenging run!

Here's a screenshot at the end of the walk and before I stopped it. I am old, but not so slow that I went .17 miles in 18 minutes!

I'm happy to provide logs if there's any way to do that.

 

[BrianGGG]

Glad that helped. I am still a bit worried that @BrianGGG was also experiencing it though.

Unfortunately, I am now stuck in Map-Only with no usage of the crown to zoom in/out. I have restarted WOD and the Watch itself, and I can't get it to work anymore.

I'm still able to use the crown in workouts, though. Not sure why it's Map-Only at this point ...

 

[cfc]

Unfortunately, I am now stuck in Map-Only with no usage of the crown to zoom in/out. I have restarted WOD and the Watch itself, and I can't get it to work anymore.

I'm still able to use the crown in workouts, though. Not sure why it's Map-Only at this point ...

I have found and fixed that problem in the code so it will be fine in the next beta.

In the meantime it should work if you start a workout with a map visible and then end it, and only then go to the Map Only mode. The current beta is remembering whether a map was used during a workout in order to decide whether or not to allow zooming. In the next beta it knows to always allow it when in Map-Only mode

 

[cfc]

BETA Feedback

Sorry, I have a weird one that I doubt I'll be able to reproduce.
I think the sequence is:

I did an Outdoor Walk
A few minutes into it, I wanted to know what time it was
I am old and can't see the small print above, so I exited out to the main screen
I double-clicked the crown to go back to WOD
When I came back, the workout time kept working as normal, but the mileage was stuck and did not move again
When I finished my walk, I long pressed and hit END.
Rather than go to the completed screen, WOD completely stopped and my walk was not recorded in WOD history or in Apple Health

Very strange indeed, and I have only seen this once. I am very glad that it was a walk that was forgotten, not a challenging run!

Here's a screenshot at the end of the walk and before I stopped it. I am old, but not so slow that I went .17 miles in 18 minutes!

I'm happy to provide logs if there's any way to do that.

That is a strange one. Please could you see if you have any diagnostic logs for that time. To do this go to Apple's "Watch" app on the iPhone and tap General and then Diagnostic Logs. If there is one for the time of the problem then please email it to me at info@workoutdoors.net. If they appear as “null” when you try to send them then please try again in an hour or so as they sometimes seem to take a while to be available.

Also, were you maybe running another workout app at the same time? WatchOS does not allow that and it could cause strange issues like you were seeing.

 

[leescottdavis]

When I finished my walk, I long pressed and hit END.
Rather than go to the completed screen, WOD completely stopped and my walk was not recorded in WOD history or in Apple Health

Are you on the WatchOS10 beta? The freeze after hitting END is similar to the behaviour experienced in WOS10.

 

[zach471]

BETA Feedback

Sorry, I have a weird one that I doubt I'll be able to reproduce.
I think the sequence is:

I did an Outdoor Walk
A few minutes into it, I wanted to know what time it was
I am old and can't see the small print above, so I exited out to the main screen
I double-clicked the crown to go back to WOD
When I came back, the workout time kept working as normal, but the mileage was stuck and did not move again
When I finished my walk, I long pressed and hit END.
Rather than go to the completed screen, WOD completely stopped and my walk was not recorded in WOD history or in Apple Health

Very strange indeed, and I have only seen this once. I am very glad that it was a walk that was forgotten, not a challenging run!

Here's a screenshot at the end of the walk and before I stopped it. I am old, but not so slow that I went .17 miles in 18 minutes!

I'm happy to provide logs if there's any way to do that.

I had that exact same issue. Time kept going, mileage stopped. I was able to recover some of the file but it had not recorded everything. I also submitted a crash report via TestFlight.

 

[cfc]

I had that exact same issue. Time kept going, mileage stopped. I was able to recover some of the file but it had not recorded everything. I also submitted a crash report via TestFlight.

Thanks for submitting the report. It said you were using watchOS 10 so I added it to my list of things to look into when I start looking at that.

At the moment I am catching up with the bugs which I can reproduce on watchOS 9. There are now 300+ testers so I am getting a lot of great feedback and focussing on watchOS 9 first. WatchOS 10 still seems very flaky from the point of view of WorkOutDoors (with both the release version of the app and especially with the beta version).

I was hoping that watchOS 10 would be more stable by now, but I am beginning to suspect that Apple won't be fixing whatever they have changed which is breaking the app.

 

[leescottdavis]

That said, I have proven twice that after pressing END, if you lower your wrist, then raise it, the delay is eliminated, and it goes to the summary screen. I would be intrigued to know if anyone on WOD4.x gets the same issue on WOS10. I suspect they don't.

 

[cfc]

That said, I have proven twice that after pressing END, if you lower your wrist, then raise it, the delay is eliminated, and it goes to the summary screen. I would be intrigued to know if anyone on WOD4.x gets the same issue on WOS10. I suspect they don't.

The user interface in the new version has been completely rewritten in a different coding language so there will be some things that watchOS 10 will break in the old version but not the new version, and vice-versa.

I had hoped that by using Apple's latest coding language (SwiftUI) then it would be less likely to be broken by whatever Apple has changed in watchOS 10. However that doesn't seem to be the case. I guess that SwiftUI is relatively new and still being changed significantly with each release of watchOS.

 

[zach471]

Thanks for submitting the report. It said you were using watchOS 10 so I added it to my list of things to look into when I start looking at that.

At the moment I am catching up with the bugs which I can reproduce on watchOS 9. There are now 300+ testers so I am getting a lot of great feedback and focussing on watchOS 9 first. WatchOS 10 still seems very flaky from the point of view of WorkOutDoors (with both the release version of the app and especially with the beta version).

I was hoping that watchOS 10 would be more stable by now, but I am beginning to suspect that Apple won't be fixing whatever they have changed which is breaking the app.

Amazing. Thanks. I knew 10 was causing issues so I didn’t want to cause a stir or post. Appreciate you looking at that.

 

[BrianGGG]

Thanks for submitting the report. It said you were using watchOS 10 so I added it to my list of things to look into when I start looking at that.

At the moment I am catching up with the bugs which I can reproduce on watchOS 9. There are now 300+ testers so I am getting a lot of great feedback and focussing on watchOS 9 first. WatchOS 10 still seems very flaky from the point of view of WorkOutDoors (with both the release version of the app and especially with the beta version).

I was hoping that watchOS 10 would be more stable by now, but I am beginning to suspect that Apple won't be fixing whatever they have changed which is breaking the app.

Thanks to all for looking at this.

I just wanted to add that I am using WatchOS9 (no beta) and I was not running any other exercise programs on my watch at the same time.

I also don’t have any crash information to share. Hopefully this was a one time problem.

 

[GJARTS]

BETA Feedback

Sorry, I have a weird one that I doubt I'll be able to reproduce.
I think the sequence is:

I did an Outdoor Walk
A few minutes into it, I wanted to know what time it was
I am old and can't see the small print above, so I exited out to the main screen
I double-clicked the crown to go back to WOD
When I came back, the workout time kept working as normal, but the mileage was stuck and did not move again
When I finished my walk, I long pressed and hit END.
Rather than go to the completed screen, WOD completely stopped and my walk was not recorded in WOD history or in Apple Health

Very strange indeed, and I have only seen this once. I am very glad that it was a walk that was forgotten, not a challenging run!

Here's a screenshot at the end of the walk and before I stopped it. I am old, but not so slow that I went .17 miles in 18 minutes!

I'm happy to provide logs if there's any way to do that.

Same here. WatchOS 10 latest beta. Workout ended without a reason. END button not working.
With watchOS 9 this was not a problem.

 

[Miggui]

hi ian, on the beta, with watchOS 9, during my run, I noticed a lag time on the AOD. the map doesn't update when I run, only when I raise my wrist. this delay is about a second before my positioning on the map is in the right place. I don't know if this has already been reported.

 

[iamasmith]

Same here. WatchOS 10 latest beta. Workout ended without a reason. END button not working.
With watchOS 9 this was not a problem.

I'm running the public beta of 10 but the release version of WOD, I just hit the crown when this happens and then open WOD again and it shows my 'End Workout?' prompt (I got sick of accidentally ending it so I enabled the additional prompt).. choosing that seems to record mine just fine. Not perfect but it's a workaround.

 

[cfc]

I'm running the public beta of 10 but the release version of WOD, I just hit the crown when this happens and then open WOD again and it shows my 'End Workout?' prompt (I got sick of accidentally ending it so I enabled the additional prompt).. choosing that seems to record mine just fine. Not perfect but it's a workaround.

I have found out what is happening here. WatchOS 10 is not informing the app that the screen is now visible after the menu has disappeared, like it used to in previous versions. This is why going to another screen by using the crown and then going back to WOD works, because then watchOS 10 informs the app that it is now visible.

I have no idea why that has changed but I have implemented a workaround in the code that will be in the next beta.

 

[cfc]

hi ian, on the beta, with watchOS 9, during my run, I noticed a lag time on the AOD. the map doesn't update when I run, only when I raise my wrist. this delay is about a second before my positioning on the map is in the right place. I don't know if this has already been reported.

The map doesn't update when your wrist is lowered. Sorry about that. Although I have found that this isn't really a problem because the map is hard to see anyway when your wrist is lowered, unlike the metrics.

I tried to get the map to update when I first rewrote the AOD version and it didn't work. So I put in code to make sure that it doesn't even try to update when your wrist is down, so that it does not waste battery. However recently I have noticed it occasionally updating, so I may revisit that before release.

 

[BrianGGG]

Beta Question

Not sure about these Start Options. I’d be grateful for a detailed explanation of all four new options.

My ideal case at startup is: I want to first pick an interval. if I have a sensor defined for that workout type, I’d like to wait until the sensor connects and then automatically start the workout (no start button necessary). This is what I think always happened in the Release version.

With the beta version I had all four Start options on. I chose an interval with my heart sensor accidentally off. The interval just started without incident.

I didn’t realize until the end of my run that sensor was off and it used my watch for heart rate. Not sure how that happened.

Am I right that there is something wrong here ?

 

[cfc]

Beta Question

Not sure about these Start Options. I’d be grateful for a detailed explanation of all four new options.

My ideal case at startup is: I want to first pick an interval. if I have a sensor defined for that workout type, I’d like to wait until the sensor connects and then automatically start the workout (no start button necessary). This is what I think always happened in the Release version.

With the beta version I had all four Start options on. I chose an interval with my heart sensor accidentally off. The interval just started without incident.

I didn’t realize until the end of my run that sensor was off and it used my watch for heart rate. Not sure how that happened.

Am I right that there is something wrong here ?

There are a few issues with the start options, including not showing the sensors start screen when using intervals. The next version of the beta will fix these issues.

Today I fixed the obvious problems when running on watchOS 10, so the next beta should work on that. However I still have a few outstanding bugs to fix (mainly with the start screen), so that beta won't be released for a few days.

 

[nippyjun]

Is there a setting to change the color of the current time in the upper right corner on the map in a walking workout. It can be hard to see with the default color.

 

[cfc]

Is there a setting to change the color of the current time in the upper right corner on the map in a walking workout. It can be hard to see with the default color.

The time is displayed by watchOS so the app cannot control it. However you can change the colour of the background that the app displays under the time, which can help.

To do this go to the Settings on the watch app and tap Map and then change the Time Background from Grey to Black.

 

[joeyd01]

Hi, do you still accept beta testers? I’d like to test the app and send feedback.

 

[nippyjun]

The time is displayed by watchOS so the app cannot control it. However you can change the colour of the background that the app displays under the time, which can help.

To do this go to the Settings on the watch app and tap Map and then change the Time Background from Grey to Black.

Thanks. That’s better.

 

[cfc]

Hi, do you still accept beta testers? I’d like to test the app and send feedback.

Sure - Please email me at info@workoutdoors.net. Thanks.