Sidebar Sidebar
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

Currently on the latest beta and still finding the large complication not updating, be it after 30/60 mins in the same location with clear weather changes outside or in a different location (40 miles from original location).

The location on the complication also stays the same.

All update a dream if I tap the complication or open the app.

I hate to swear but I'm finding "Dark Sky" is updating more reliably at the moment which I don't want to hear as DS is cheaper but up until now Carrot was my go to app and one that I've recommended to friends and family with and without the Apple Watch.

Any assistance would be much appreciated.
 
MakerOfCARROT said:
Usually when the complication is showing that it's currently raining, it will:

1) Show when it's supposed to stop raining if that data is available
2) Show "rain for the hour" if the data shows it's going to be raining for >1 hr
3) Show the percentage chance of rain for the *next* hour if 1 and 2 aren't available

However, it only shows those details for the near future. Once you get farther out on Time Travel, it switches to showing what the weather will be like in 3 hours from the time that's currently displayed. The different messages - "later", "in a bit", etc - are just randomly displayed so it's not always the same message.
Click to expand...

Thanks for the explanation. I just find it a little peculiar with the wording, without a change in conditions. Perhaps if there's nothing different forecast in between it should be prefaced with "still".

Also at 1:59 (11:45 from now on time travel) it's showing rain in ~3 hours. From 4 onwards it's "windy". It's confusing.
 
  • Like
Reactions: MakerOfCARROT
image.png

What should this one say? :)
 
  • Like
Reactions: dooku77
Beefburga said:
Currently on the latest beta and still finding the large complication not updating, be it after 30/60 mins in the same location with clear weather changes outside or in a different location (40 miles from original location).

The location on the complication also stays the same.

All update a dream if I tap the complication or open the app.

I hate to swear but I'm finding "Dark Sky" is updating more reliably at the moment which I don't want to hear as DS is cheaper but up until now Carrot was my go to app and one that I've recommended to friends and family with and without the Apple Watch.

Any assistance would be much appreciated.
Click to expand...

If you're not seeing any change in the complication *AT ALL* as if the complication was literally frozen (in other words, you check it at 5am and 6 hours later it's still showing the exact same temperature and conditions, a night-time icon, etc) then that's a completely new bug that no one's ever reported before. You should email me through the app so we can try debugging it, installing a non-beta version, etc.
[doublepost=1453529118][/doublepost]
nicho said:
What should this one say? :)
Click to expand...

That's either "for the hour" or "for the day". I'd never seen dual conditions come up like that back during the summer/fall when the complication was being built, maybe those really only come up during the winter. I'll make a note to filter those for length in the future. Thanks!
 
  • Like
Reactions: dooku77
Another oddity, different conditions this time but same result.

image.png

This one has two problems. Until tomorrow evening doesn't quite fit and also... It's quarter past midnight. Tomorrow evening would be continuing conditions for roughly 42 hours?

image.png
 
image.png

Are the ellipses intended to make the forecast more mysterious, or is this another bug :)

I'm enjoying this beta testing. I'll be upset when I'm back in school and have to revert to the small complication. Although I'm sure when that happens (cough one month cough) I'll have that lovely new conditions and precipitation complication to test ;)
 
  • Like
Reactions: dooku77
I think the issue is that, for some reason, the hourly condition text from forecast.io is a lot wordier for China than it is for other countries. Looking at the forecasts right now for a couple different cities in China, a lot of them have dual conditions (i.e. "rainy and breezy" or "overcast and breezy"), so I'll just have to filter them a bit better in the next update.
 
  • Like
Reactions: nicho and dooku77
Beta update! I made a bunch of adjustments to the location handling and the frequency threshold for updates, hopefully this will iron out issues with the location option you've all been helping to beta test.

If you see a location with an ampersand (&) or asterisks (*), that's there for debugging purposes. The ampersand means the location update on the Watch failed, so it defaulted back to your last cached location. The asterisks mean that the retrieval of the city name failed - you'll see between 1 and 4 asterisks, they just denote which specific line of code failed.

This way, if the changes I made don't actually help with fixing the current location updating in a timely manner, at least we'll know what specific area is failing.

Thanks again, everyone, for all your help - I really appreciate the time so many of you have put into testing CARROT!
 
  • Like
Reactions: Beefburga, testcard, dictoresno and 1 other person
MakerOfCARROT said:
Beta update! I made a bunch of adjustments to the location handling and the frequency threshold for updates, hopefully this will iron out issues with the location option you've all been helping to beta test.

If you see a location with an ampersand (&) or asterisks (*), that's there for debugging purposes. The ampersand means the location update on the Watch failed, so it defaulted back to your last cached location. The asterisks mean that the retrieval of the city name failed - you'll see between 1 and 4 asterisks, they just denote which specific line of code failed.

This way, if the changes I made don't actually help with fixing the current location updating in a timely manner, at least we'll know what specific area is failing.

Thanks again, everyone, for all your help - I really appreciate the time so many of you have put into testing CARROT!
Click to expand...

updated about an hour ago, complication was still showing "current loc..." a second ago without asterisks. where are the asterisks meant to be, at the start or the end?
 
nicho said:
updated about an hour ago, complication was still showing "current loc..." a second ago without asterisks. where are the asterisks meant to be, at the start or the end?
Click to expand...

Asterisks are at the end, but it should show up as "Unk***" if the asterisks are going to show up. The data was probably just cached from the update before you installed the latest beta - next time, you can open the main Watch app to force the complication to refresh. "Current" and "Current Location" shouldn't show up anymore on the complication.

nicho said:
Just got my first &
Click to expand...

So the watch tried to grab your latest location, but the update failed. What are your location services settings on your iPhone?

Beefburga said:
Shortly after updating the beta it started to rain outside, is this connected?
Click to expand...

Definitely related.
 
MakerOfCARROT said:
Asterisks are at the end, but it should show up as "Unk***" if the asterisks are going to show up. The data was probably just cached from the update before you installed the latest beta - next time, you can open the main Watch app to force the complication to refresh. "Current" and "Current Location" shouldn't show up anymore on the complication.



So the watch tried to grab your latest location, but the update failed. What are your location services settings on your iPhone?
Click to expand...

always on. next time i checked my watch (admittedly not for a while) it was normal, saying "Shenzhen".

As i type this, i'm seeing Unk** (when i started replying it said "Shenzhen" as usual)

MakerOfCARROT said:
Definitely related.
Click to expand...

that's how carrots are made, after all.
 
  • Like
Reactions: MakerOfCARROT
OK, so I'll try increasing the timeout for the location updates in the next seed - it's currently 3 seconds, since I'd rather have it show data for your last cached location than take 10+ seconds to update when it comes to the main app. But I could set up a separate timeout for the complication of around 10s, since it doesn't really matter how long that update takes.
 
Quick update on today's beta. Arrived home from a location 20 miles away. After 30 minutes at home, original location still showing, but now with an ampersand.
Edit: 45 minutes after arrival at home, now showing correct location. This is an improvement as there were occasions when original location would display for up to 2 hours.
 
Last edited:
testcard said:
Quick update on today's beta. Arrived home from a location 20 miles away. After 30 minutes at home, original location still showing, but now with an ampersand.
Edit: 45 minutes after arrival at home, now showing correct location. This is an improvement as there were occasions when original location would display for up to 2 hours.
Click to expand...

Yeah, this has been good because we can now confirm that the app is *trying* to update its location. watchOS 2 just has some issues with location updates (see other devs who have been having similar issues) that I'll have to figure out workarounds for.
 
Just arrived home about 30 minutes ago. Tapped on small complication (temp, precip chance) on modular face. App came up with location I was at around 4:30pm EST. But in 10 seconds or so, my home location swapped in. No ampersands or anything.
 
  • Like
Reactions: MakerOfCARROT
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