Is there a special trick to force maps to download to the watch? I somehow got this to work a couple months ago, but now it's just stuck and nothing seems to work.
- On 17.6 iPhone, 10.6 watch
- Rebooted both phone and watch, verified the watch is connected to the phone
- Have the app open on both my phone and watch, go to various menus on watch, let it sit on the map
- Have tried with both the watch on my wrist and on the charger
The app is stuck at: "No Downloads Required. Run app on watch to enable transfers. Transferred 0/3 (0%)". Has been on this screen for over 30 minutes with no change.
The usual reason for problems is if you have another app which is transferring data (usually an audio app). WorkOutDoors then needs to wait until that app is finished. So it is worth waiting a few hours (sometimes longer) and trying again later.
Some people have reported that starting a dummy workout on the watch can help because it gives the app higher priority in the eyes of watchOS. However I never get any file transfer problems (I don’t often use audio apps) so I can’t confirm this.
If waiting and a dummy workout don't help then the order of things to try is:
- reboot both devices (note that if you do this before waiting then you could just restart the other data transfer and have to wait even longer).
- uninstall the watch app; reboot both devices; re-install the watch app.
- unpair the watch from the phone and then re-pair it.
Note that if you reinstall the watch app or unpair then you will then need to send the data from the iPhone app to the watch app. This can be done by going to the Settings tab and tapping File Management and then "Send Yesterday’s Watch Settings", "Send Screens to Watch” and “Send Interval Schedules to Watch”. If you want then you can also send routes or workouts individually. They can’t all be sent at once because they are too large.
Unfortunately the app is at the mercy of iOS/watchOS for file transfer. The mechanism they provide has always been a bit flaky. The degree of flakiness has varied over the years but is relatively bad at the moment. I assume that it is related to whatever they did to break the file transfer confirmation in iOS 17.5 (which they still haven't fixed).
I hope that helps.