i believe that functionality will be fixed soon, once the beta is not beta.
Thanks
i believe that functionality will be fixed soon, once the beta is not beta.
Interestingly I had a 4 hour journey in my car this afternoon. I set location in the large complication, and kept an eye on it. Without opening the app at all, the location updated around 4 times during the journey. However, each update showed the location where I had been roughly an hour or 60 miles earlier. Now I'm home, complication hasn't updated from last journey location 2 hours ago.Can you confirm the following:
(I've upgraded to premium)
When does the watch complications automatically update (without the need to open the app on the watch)? I'm sure I read it was every 30mins.
What mileage do you have to travel for the app to realise you're in a new location and to update the complication?.
I only ask as mine seems to only update if I activate the app on my watch.
Interestingly I had a 4 hour journey in my car this afternoon. I set location in the large complication, and kept an eye on it. Without opening the app at all, the location updated around 4 times during the journey. However, each update showed the location where I had been roughly an hour or 60 miles earlier. Now I'm home, complication hasn't updated from last journey location 2 hours ago.
Interestingly I had a 4 hour journey in my car this afternoon. I set location in the large complication, and kept an eye on it. Without opening the app at all, the location updated around 4 times during the journey. However, each update showed the location where I had been roughly an hour or 60 miles earlier. Now I'm home, complication hasn't updated from last journey location 2 hours ago.
Agreed. Can't fault the customer service. Particularly as we're just insignificant meatbags![]()
When does the watch complications automatically update (without the need to open the app on the watch)? I'm sure I read it was every 30mins.
What mileage do you have to travel for the app to realise you're in a new location and to update the complication?
Yes, it should be updating its data every 30 minutes - i.e. if you look at your Watch at 4:59 and then again at 5:00 (and at 5:29 and 5:30), the temperature should change as long as the temperature is actually changing noticeably enough throughout the day. If you spin the Digital Crown to activate Time Travel, you'll notice the data changing at those half-hourly bounds. (If you're using a small complication slot, you might have to spin it ahead a few hours to see the temperature change if it's staying pretty level where you're located - the large slot displays more data, so it's easier to see changes throughout the day there.)
It should be less than 2km to activate a location change update if you have location services set to "always", but it's possible that isn't actually getting sent across to the Watch to update the complication. Updating the complication from the iPhone was always something that sometimes worked, sometimes didn't when watchOS 2 first came out.
I think what's likely happening is that the complication data *is* getting updated, but the location update is failing, so it just looks like it's stuck with old data because the location label is showing a location from earlier in the day. Maybe in the next beta seed, I'll add some sort of symbol like an asterisk to the complication when the location update fails so we can see if that's really what's happening in these cases.
Thanks for the response.
All day today I wasn't getting an automatic update on the large complication and that includes traveling 10 miles and waiting over 45mins in the new location. (Please note that I didn't just sit there in the new location watching my AW waiting for it to change, I'm not that sad......... I looked on the Internet for vinyl flooring while I waited)
The app (complication) didn't and wouldn't update until I activated the app.
Sorry to go on but it's Saturday, I've had a drink and I really should be out but the weather is awful....... *activates the app, oh! It's alright now.
The latest beta update fixes a location issue as you can read in the posts between me and the developer. I drive 15 miles to work and within usually 30-45 mins of arriving there, my location is updated and the app shows the correct weather data.
I've just returned from a brief shopping trip to the town where I live (so effectively the same location) and location in the large complication is showing "Unknown". First time I've seen this behaviour.
Edit: after two hours, correct home location has re-appeared. Server-side issue?
"Unknown" should only show up if the Watch failed to download the location name from Apple's servers (they have a service that takes in a longitude/latitude and spits back the city name, state, etc).
Just got this screen. Now this is rare, as the newest updated beta has been working nearly flawlessly since you fixed the last location issue. Just wanted to see if this "current" location name is somewhat normal and could show from time to time. I guarantee if I look again in a little bit, it will be fixed on its own.
Ah, the dreaded "unknown!" Just as an aside, I'm finding that it's currently taking around 2 hours from arriving home from work before location is changing. Earth's magnetic poles flipping polarity? Damn meatbags![]()
I have a couple things to try with getting the location label to update more frequently, hopefully one of those will work!
Today's forecast is almost entirely rain from now on. the large complication (using time travel) seems to alternate between - rain: later, later on, in a bit, by and by, in ~3 hours.
Is this expected? It's already raining according to the forecast, it seems very peculiar to tell me it's going to rain later if it already is?
The latter is the strangest one. Why would it tell me it's going to rain in about 3 hours when it already is raining...