I have the same issue with watchOS 10.0.1, used to work on watchOS 10.0 (although I moved to 15PM and had to set up the watch again).
Last edited:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Current location weather - bug in watchOS 10 beta?
- Thread starter falkirk81
- Start date
-
- Tags
- beta watch weather widget
- Sort by reaction score
Having the same issue here ever since IP15 upgrade. I've tried restoring watch 3 times, starting watch from scratch, reseting all location & privacy with no luck. Finally got it working last night after simply deleting/reinstalling weather app from iPhone! But this morning it is broken again.
That worked for me for weather compliance except for Sunrise/Sunset which continues to be - - .
Settings - General - Reset and then Reset Location and Privacy
I've tried that, as well as setting up both my phone and watch as new devices and still the issue persists......
Looks like its something only Apple will be able to sort with an update
Last edited:
The location and privacy reset didn't fix it for me. The only way to fix it temporarily is to change the watch face and then back to my regular watch face. It goes back to -- after about an hour, though. I guess only Apple can permanently fix it.
I have the same problem but I think it’s related to the fact that “current location” doesn’t even show as an option in my apple watch weather app. If I go into the app I only see the pre set locations.
rbart said:
You can try to reset all of your location settings to the factory default on your iPhone, go to Settings > General > Transfer or Reset [device], tap Reset, then tap Reset Location & Privacy.
When your location and privacy settings are reset, apps will stop using your location until you grant them permission.
this fix works only for a few hours unfortunately
.. in my case once i reset the location authroizations everything seemed to work fine initially , a little over a a couple of hours later , the same problems started to reoccurIt's working for most people without any issue.this fix works only for a few hours unfortunately
You should have another problem.
The issue is that after you select the complication the default city for weather switches away from "current location". Check it by going to settings->weather on your apple watch.
You can temporarily fix it by force quitting the weather app and restarting your watch. But if you click on the complication again the issue will come back.
You can temporarily fix it by force quitting the weather app and restarting your watch. But if you click on the complication again the issue will come back.
I turned off location services and turned it back on and the temp now shows on the watch.
It doesn’t show all of the cities I have on the phone but it’s a step forward
It doesn’t show all of the cities I have on the phone but it’s a step forward
Add a city in your iPhone and it will force sync to the watch
Then you can delete the added city
@rbart almost all of the issues were fixed by followng the reset location authorizations method thanks to your advise , location issues and the smaller circular weather compications too work as intended but barring one issue , and that is the larger hourly weather conditions complications/widgets keep saying ''loading weather'' often .. these hourly weather widgets which are also present in the smart stack also keeping saying the same ''loading weather'' message ...even in the modular watch face . when i place any of the weather widgets in the large middle slot , most of the times is says ''loading weather''
I reported this bug to Apple during beta 7/8 and have no response. The problem goes deeper than just Weather - it seems to be a location services bug in general.
I was working on a new app with location data, and after installing my app the first time, location for my watch app no longer worked. The app on the phone was fine, but the watch app with the connected location permissions couldn't request permissions, and according to the OS it already had permissions to get location. But when I make a location request, it would just return an error that the app doesn't have permissions.
Built a simple demo project and submitted it with my radar, it breaks 100% of the time if you delete one of the apps and reinstall, and can't be recovered after that point. I ended up shelving the app for now as the watch app having location data is crucial to it's function. It works perfectly on watchOS 9, even connected to an iOS 17 device.
I was working on a new app with location data, and after installing my app the first time, location for my watch app no longer worked. The app on the phone was fine, but the watch app with the connected location permissions couldn't request permissions, and according to the OS it already had permissions to get location. But when I make a location request, it would just return an error that the app doesn't have permissions.
Built a simple demo project and submitted it with my radar, it breaks 100% of the time if you delete one of the apps and reinstall, and can't be recovered after that point. I ended up shelving the app for now as the watch app having location data is crucial to it's function. It works perfectly on watchOS 9, even connected to an iOS 17 device.
Exactly, I have spent one week trying to fix my app (YouRace) which wasn't getting access to GPS on my watch.
Locations look correct, pair/unpair did nothing.
Reset as new did nothing
The problem was only fixed by resetting all location authorizations on the iOS side.
I think all apps that rely on GPS could have the same issue.
It's a bug that came with iOS17/watchOS10 and not only impacting weather.
Weather is probably the visible part of the iceberg as most people have a weather widget on the watchface.
That's right. I also have the sunset/sunrise and weather problems myself. This data is not displayed correctly.
Interestingly, the problem can be solved in the short term:
Turn on WiFi on the watch!
Close the respective app on the watch and reopen it. Even if the iPhone is not connected to WiFi, the respective complication will appear again. For me, a GPS tracking bug is responsible for all the problems. Presumably this will be fixed in 10.1. Hopefully...
Interestingly, the problem can be solved in the short term:
Turn on WiFi on the watch!
Close the respective app on the watch and reopen it. Even if the iPhone is not connected to WiFi, the respective complication will appear again. For me, a GPS tracking bug is responsible for all the problems. Presumably this will be fixed in 10.1. Hopefully...