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.
Apps CARROT Weather's customizable complications
- Thread starter MakerOfCARROT
- Start date
- Sort by reaction score
Back when watchOS 2 was launching, I had to separate the location updates from the actual weather data updates because the Watch would sometimes take a very long time to return location data. I think some of those issues have since been addressed in watchOS updates. So in the next beta seed, I'll try making the location updates as frequent as the weather updates and see if anyone notices any issues with performance.
[doublepost=1452140504][/doublepost]
If you have the Utility face selected, you can switch between grayscale and multicolor icons.
The Barometer Complication is it pulling data from the Provider or using the onboard Barometer?
I've got the Beta version on the iPhone (I assume there is not one for the Mac). I'm in Little Rock, AR where it is overcast & raining on & off. Both the iPhone app & the Watch say it is partly sunny. My numerous other apps say it is raining.
Just the provider at the moment - I may add an option to use the device's barometer in the future, though.
That's likely an issue with my weather data provider, forecast.io, rather than a bug in the beta. Sometimes their algorithms misreport rain due to issues with their radar coverage.
I've noticed this as well.
I'm on the Premium version (BETA) and notice I have to tap the complication for it to update after traveling to a new destination.
Have done now. Sorry I sent that before I saw your later response to another forum user!
Same here. Never changes the city unless I force change it by using force touch.
Just put out a new seed with more aggressive location updates - also found a bug that would prevent location updates from happening if the update was coming via background refresh or the significant location change service on the iPhone. Hopefully that's what was causing the issue for you guys.
I only really leave the house on the weekends because CARROT keeps me chained in a small closet toiling away on her, so I'm relying on you guys to help me test the location stuff
I only really leave the house on the weekends because CARROT keeps me chained in a small closet toiling away on her, so I'm relying on you guys to help me test the location stuff
Tomorrow I'm traveling from Romford in the outskirts of London, into central London and then out to Cardiff in Wales (and back). I'll keep an eye on the location throughout the journey to see how it updates. I'll post a bug report if there's any unexpected behaviour.
Yeah, I set it to only update if it's been >30 minutes. (And make sure you have location services set to "always" for CARROT.)
The Apple Watch doesn't allow complications to update continuously throughout the day - it gives you an allotted amount of time that you're allowed to run each day, and once you exceed that threshold you can't update the complication's data any more until the following day. So I don't want to risk anything more aggressive than every 30m (Apple actually recommends every 60m).
I thought that having it use the cell phone antenna for location made it so we didn't need to rely on gps. I don't wanna have location services set to always. It's a battery drain. I thought the way around that was how you set it up to use cell triangulation as opposed to gps.
The only way to use that cell triangulation service is to set location services to always. Otherwise, CARROT can't access your location data when the app is inactive since you've set your permissions to block access to that data...
As a reminder, just because the arrow is appearing in the status bar, that doesn't mean that the GPS is active. It just means an app has been granted access to your location when it's not being used.
Last edited:
Just to follow up, you don't need to have location services set to "always" for the complication to work, but you do for the "significant location change" service I was referring to earlier. That service is one of the methods I was using to ensure the complication stays as up to date as possible.
Early on in this thread, I mentioned that developers can register for their complication to update every 30m, but the Watch is what decides when the complication actually updates based on factors like wifi availability, battery life, etc. So the complication only updates sometime *after* 30m - it might be 35m, it might be 60m. So I added in a couple different tricks on the iPhone side, like background fetch and significant location change monitoring, to force the complication to update more frequently at a rate closer to the 30m update interval.
If you're concerned about the location updating frequently based on your travels throughout the day, it's probably a good idea to at least try turning it on. If you find it does affect your battery life, you can just turn it back off.
I really never should have given people the option to switch to "while using" because it just causes a lot of confusion. And it's going to be a bit of a problem once native notifications get added in, since that'll require "always" in order for it to work. (That's what you get for implementing feature requests that literally 1 person asked for, and you think to yourself "oh that won't be that much work, why not just spend 5 minutes adding that in?")
Early on in this thread, I mentioned that developers can register for their complication to update every 30m, but the Watch is what decides when the complication actually updates based on factors like wifi availability, battery life, etc. So the complication only updates sometime *after* 30m - it might be 35m, it might be 60m. So I added in a couple different tricks on the iPhone side, like background fetch and significant location change monitoring, to force the complication to update more frequently at a rate closer to the 30m update interval.
If you're concerned about the location updating frequently based on your travels throughout the day, it's probably a good idea to at least try turning it on. If you find it does affect your battery life, you can just turn it back off.
I really never should have given people the option to switch to "while using" because it just causes a lot of confusion. And it's going to be a bit of a problem once native notifications get added in, since that'll require "always" in order for it to work. (That's what you get for implementing feature requests that literally 1 person asked for, and you think to yourself "oh that won't be that much work, why not just spend 5 minutes adding that in?")
I switched it to always to try it out and see what happens. Thanks for the help. I didn't know that just because the icon was there doesn't necessarily mean that the gps is currently being used. Right now carrot is using 1% of my battery over the past 24 hours. I'll test to see how much higher it gets.
Last edited:
My location info has been showing/working all day. I have been in the same location for the past 6 hours. Now all of a sudden the complication says "current location" even though the app properly states my current location name. Manually updating the app and manually selecting my current location won't update the complication even though the app says it is. Is this a bug? The location data is set to always.
Dear Carrot
I've got a major problem which has been happening all through the festive period.
Almost every day it's been raining stopping me and my family going out and when we do we find ourselves getting really wet.
This only started after upgrading to you premium service. If I cancel my premium service will my weather improve because it's starting to really effect my hair.
Any help would be greatly appreciated
I've got a major problem which has been happening all through the festive period.
Almost every day it's been raining stopping me and my family going out and when we do we find ourselves getting really wet.
This only started after upgrading to you premium service. If I cancel my premium service will my weather improve because it's starting to really effect my hair.
Any help would be greatly appreciated
Ok so I have been in a different town for 2 hours and just picked up my watch only to see the old location still on the screen. It never switched to my new one. I tapped the complication and the app refreshes itself to the new location. Then the complication changed. So even with background app update on and location services set to always, the location and weather data isn't updating as it should. Mostly the location data, since the weather data corresponds to the location.