Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Maps take a long time to load

SDColorado said:
Correct. Resetting network settings will cause you to lose all stored wifi passwords, but can be a useful tool in solving connectivity issues and glitches. I just re-do the ones that are important. In a sense, it is a bit of a purge to get rid of old settings no longer needed and start fresh. Do I *really* need a wifi password stored for a coffee shop in Seattle that I visited 5 years ago, for example?

The Bluetooth connection will be re-established by pairing the watch again, which you have done.

Glad to hear that it appears to be working as expected now :)
Click to expand...

Yes unpairing fixed it.
 
  • Like
Reactions: SDColorado
Its starting to act up again. Rebooting the watch and the phone did nothing so I have given up. This is a bug. I submitted feedback to apple. I am no going to pair my watch again over this as I will just use my phone for maps.
 
jwolf6589 said:
Its starting to act up again. Rebooting the watch and the phone did nothing so I have given up. This is a bug. I submitted feedback to apple. I am no going to pair my watch again over this as I will just use my phone for maps.
Click to expand...

I'm curious if this happens when you are in wifi coverage or only on cellular? I know in another thread you mentioned you have sprint, which I also have, and my maps will load slowly sometimes on cellular but are fine on wifi. I'm pretty sure it has to do with the strength of the cellular signal, rather than a bug in the watch software.
 
mk313 said:
I'm curious if this happens when you are in wifi coverage or only on cellular? I know in another thread you mentioned you have sprint, which I also have, and my maps will load slowly sometimes on cellular but are fine on wifi. I'm pretty sure it has to do with the strength of the cellular signal, rather than a bug in the watch software.
Click to expand...

I have it anywhere. Its not the signal strength, its a bug in the software.
 
SDColorado said:
There has been no discussion in the dev forums about there being a bug with the maps loading slow. No mention of it. It must be a very under the radar bug.
Click to expand...
Actually it is probably more of an individual anomaly of some type and not a bug at all.
 
Julien said:
Actually it is probably more of an individual anomaly of some type and not a bug at all.
Click to expand...

Yes, there was a more widespread issue with maps loading slow on the watch back in 2015 and again in late 2016, but both were well documented and you will see *many* results if you do a Google search. Most recently circa October 2016. Google turns up nothing for 2017, that I could find, not that I am going to go back too many pages. Nor does there appear to be anything recent in the Apple Seed Discussions.

If someone feels there is a bug that has been missed, by all means, submit it. But I would think it would be more widely reported if it was actually a bug. A lot of people use the maps feature.
 
SDColorado said:
There has been no discussion in the dev forums about there being a bug with the maps loading slow. No mention of it. It must be a very under the radar bug.
Click to expand...

Called Apple care and the tech support rep had the same problem with maps not loading at all.
 
jwolf6589 said:
Called Apple care and the tech support rep had the same problem with maps not loading at all.
Click to expand...

So you said, before you unpaired and repaired and it worked.... until it didn't. Now it is working again after a software update, but still not being discussed or addressed as a bug in the build discussions and no mention that it was among the fixes in the latest build.

BUT, If you feel it is a bug, trigger a sysdiagnose on your Apple Watch, A co-sysdiagnose is automatically triggered on your paired iPhone to collect necessary information from both devices.

Press and hold both the Digital Crown and side button for one second, then release.

After releasing the buttons, you should feel your Watch vibrate.

Allow two minutes for the diagnostics to complete.

Connect your paired iPhone to iTunes, sync, and retrieve the iOS and watchOS sysdiagnoses from ~/Library/Logs/CrashReporter/MobileDevice/[Your iPhone]/DiagnosticLogs/sysdiagnose.

Both sysdiagnoses will have the same timestamp, and one will begin with watch_

Use Feedback Assistant on OS X to upload these additional files.
 
SDColorado said:
So it is a series 2? Mine only takes a few seconds from hitting My Location to loading the maps.

I am not sure what Apple Support had you try, but if you don't want to wait until the next update and want to experiment a little further, there are a few things you can try (and may have already tried):

- On your iPhone, check that Location Services is enabled. Settings -> Privacy -> Location Services. Turn them on, check that maps is set to "while using."

- Close all apps and restart both your watch and your phone.

- Unpair and re-pair your watch. The watch app will make a backup of your watch automatically when unpairing, but you may have to setup a couple of things such as Apple Pay credit cards, passcodes etc.

I have heard of that more commonly back in '15/'16 when the watch was first released, but not recently, which is why I asked how "common" it was, since the Apple Support rep seemed to indicate it was. Interesting.
Click to expand...
I have a Series 2 and used to have a Series 0. The Series 2 is very inconsistent. Sometimes the maps are displayed, sometimes they're not. I always need to restart the Watch to fix it.
 
  • Like
Reactions: jwolf6589
sflomenb said:
I have a Series 2 and used to have a Series 0. The Series 2 is very inconsistent. Sometimes the maps are displayed, sometimes they're not. I always need to restart the Watch to fix it.
Click to expand...

I am the same, had (still have) a Series 0, now a Series 2. Haven't had any issues with the maps, but more importantly if people are having issues, they should submit them via feedback. Apple doesn't spend any time reading Mac Rumors, so the discussion needs to hit the official Apple channels. :)
 
SDColorado said:
So you said, before you unpaired and repaired and it worked.... until it didn't. Now it is working again after a software update, but still not being discussed or addressed as a bug in the build discussions and no mention that it was among the fixes in the latest build.

BUT, If you feel it is a bug, trigger a sysdiagnose on your Apple Watch, A co-sysdiagnose is automatically triggered on your paired iPhone to collect necessary information from both devices.

Press and hold both the Digital Crown and side button for one second, then release.

After releasing the buttons, you should feel your Watch vibrate.

Allow two minutes for the diagnostics to complete.

Connect your paired iPhone to iTunes, sync, and retrieve the iOS and watchOS sysdiagnoses from ~/Library/Logs/CrashReporter/MobileDevice/[Your iPhone]/DiagnosticLogs/sysdiagnose.

Both sysdiagnoses will have the same timestamp, and one will begin with watch_

Use Feedback Assistant on OS X to upload these additional files.
Click to expand...

Thanks for this. The next time maps refuses to load maps I will use this feature.
 
  • Like
Reactions: SDColorado
jwolf6589 said:
Thanks for this. The next time maps refuses to load maps I will use this feature.
Click to expand...

That's the best way to get it directly to the dev team working on the builds :)
[doublepost=1494991667][/doublepost]In addition to what I posted above, those sysdiagnose files contain data that may assist them in determining whether or not it is a bug in the build, or an isolated issue with your particular watch (data corruption, conflict issue with another app, etc.).

You may already be familiar with how to locate the ~/Library/, but just in case you are not, from Finder click "Go" in the menu and hold down the Option key. You will see a hidden menu item "Library" appear in the drop down menu. From there drill down as described in the instructions above.

That sysdiagnose file contains data such as error logs, crash reports, wifi info etc.

One other thing you may wish to try, if it slows down again, is on your phone, go to Settings -> General -> Language & Region. Briefly change it to a different country, wait for the change process to complete and then set it back to the United States. My understanding is that this will force your phone to re-download the region maps.
 
  • Like
Reactions: jwolf6589
SDColorado said:
So you said, before you unpaired and repaired and it worked.... until it didn't. Now it is working again after a software update, but still not being discussed or addressed as a bug in the build discussions and no mention that it was among the fixes in the latest build.

BUT, If you feel it is a bug, trigger a sysdiagnose on your Apple Watch, A co-sysdiagnose is automatically triggered on your paired iPhone to collect necessary information from both devices.

Press and hold both the Digital Crown and side button for one second, then release.

After releasing the buttons, you should feel your Watch vibrate.

Allow two minutes for the diagnostics to complete.

Connect your paired iPhone to iTunes, sync, and retrieve the iOS and watchOS sysdiagnoses from ~/Library/Logs/CrashReporter/MobileDevice/[Your iPhone]/DiagnosticLogs/sysdiagnose.

Both sysdiagnoses will have the same timestamp, and one will begin with watch_

Use Feedback Assistant on OS X to upload these additional files.
Click to expand...

Just did the diagnostic on the watch and went to that folder but the watch file is nowhere to be found.

sysdiagnose_2016.12.21_18-37-48-0700.tar
sysdiagnose_2017.05.18_16-16-32-0600.tar
 
jwolf6589 said:
Just did the diagnostic on the watch and went to that folder but the watch file is nowhere to be found.

sysdiagnose_2016.12.21_18-37-48-0700.tar
sysdiagnose_2017.05.18_16-16-32-0600.tar
Click to expand...

Are you certain you are following all the steps, counting out a second depressing both of the buttons, getting the double tap haptic from the watch as confirmation, waiting at least 2 minutes for it to complete, and then attaching the phone to your computer and then syncing the phone via iTunes?

In step 2 of the sync, you should see a status message "copying diagnostic information"

Then in the folder, I mentioned above, you should have a file such as:

co-error-watch_sysdiagnose_2017.05.18_18-06-27-0600.tar

 
Last edited:
Update: the Maps have been working for me on the watch ever since I upgraded to the newest version of watchOS.
 
  • Like
Reactions: SDColorado
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back