Well scratch that, I changed the complication (via the watch) to another app, and changed it back, and the number is back... so I'm not sure if it's a Carrot bug or an Apple bug...?
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
Well scratch that, I changed the complication (via the watch) to another app, and changed it back, and the number is back... so I'm not sure if it's a Carrot bug or an Apple bug...?
All good so far and Morning/Evening Reports arriving on time. Noticed that changes in location are updated rapidly in Large Slot complication. Just need a Precipitation Alert now...probably Friday in the UK.
My problem was the fact that I needed to delete the beta profile. I didn't realize putting the beta on the phone would also install a separate watch beta profile. Everything works now.
Do you know if we should still expect the morning reports when the watch is not being worn? I didn't receive my report this morning, but I was still asleep when I had it set to come through.
Ah, that may explain it. My preference would be to JUST get it on the Watch and not have it show up on my phone, as it did last night at 9. Right now the only Notifications preference for CarrotWeather on the Watch app is for mirroring, so I guess I'll just have to stay off my phone at that time!
No. I have had the public beta on one Mac and on my iPhone. I am not a developer, so I did not even consider putting it on the watch.
I am a little confused. I was already running Developer iOS 10 as well as AW3.
I saw a TestFlight CARROT Beta, so I updated it. When I go to the AW Apps, it shows that I "could" download the CARROT app.....is this showing because CARROT is not recognizing that I have the CARROT beta installed?
Should I remove CARROT Beta and just install from app store (Not sure which one is the newest one).
Thank you everyone!
I saw a TestFlight CARROT Beta, so I updated it. When I go to the AW Apps, it shows that I "could" download the CARROT app.....is this showing because CARROT is not recognizing that I have the CARROT beta installed?
Should I remove CARROT Beta and just install from app store (Not sure which one is the newest one).
Thank you everyone!
In that case, as there is no public beta program for the Watch, you should not have had a profile on your phone. Did you perchance install independently?
The TestFlight beta is the most up to date version, it has a couple fixes not in the App Store version (and is about to get a few more). You can install the Apple Watch version via TestFlight, I believe.
@MakerOfCARROT why can't i find any kind of "restore purchases" function (is that even allowed on the app store, to not have this?) - i've lost access to my apple watch complication settings and to the notifications. i'm not a happy bunny right now...
i was not seeing any reference *at all* to premium, which was odd. is there some kind of location dependence built in the app to hide it in some countries, that could have got fried?
anyway, i say was. a reboot of both watch and phone fixed it... but the lack of information about premium outside of that screen was scary to say the least.
That's actually a bug that's been around since watchOS 2. I use Watch Connectivity (an Apple-provided framework that allows iPhone apps to talk to the Apple Watch and vice versa) to determine if an Apple Watch is paired with the user's iPhone, because I can't have the premium option appearing for users without an Apple Watch. Sometimes the Watch Connectivity framework stops recognizing that an Apple Watch is paired, though. And only a reboot of the iPhone will fix it.
This did give me an idea for a workaround for this particular bug, though: I'll make it so the premium section always appears if you've viewed it at least once. That way it won't just randomly disappear on people, leaving them confused as to where it went.
the scariest part of it was that it was still there after both my upgrade to ios 10 and watch os 3 - it just decided to disappear afterwards.
any ideas why my weather forecast will only populate for the next 5 hours when using time travel?
(i'm now on the latest beta) should it fix itself eventually?
any ideas why my weather forecast will only populate for the next 5 hours when using time travel?
I had to limit the amount of data that would show up in the timeline starting in early watchOS 3 betas. watchOS 3 is much more strict on the amount of time complications are allowed to spend caching data for the timeline, and 5 hours or so was the magic number that kept the system from complaining too much. There's a lot of extra processing going on behind the scenes that other weather apps don't bother with, like the text descriptions of upcoming weather on the Modular Large slot.
Just out of curiosity...
I watched some of the developer videos from the WWDC, and if I understand correctly, if we have Carrot set up as a complication and kept in the dock, then there are two separate events that will trigger an update... one from the complication (max 50 times per day) and one from the dock (minimum once per hour). How much are you allowed to update when those events fire off? For example, during a complication update event, are you also allowed to update the dock snapshot?
I ask because I've noticed that sometimes when I tap in to the app from the complication, the app itself has not been updated and the info can sometimes be pretty outdated and it will take several seconds to correct itself, so for example my complication said the temp was 65, but when I opened the app it said it was 53 and didn't update until I force-pressed and told it to refresh.
I watched some of the developer videos from the WWDC, and if I understand correctly, if we have Carrot set up as a complication and kept in the dock, then there are two separate events that will trigger an update... one from the complication (max 50 times per day) and one from the dock (minimum once per hour). How much are you allowed to update when those events fire off? For example, during a complication update event, are you also allowed to update the dock snapshot?
I ask because I've noticed that sometimes when I tap in to the app from the complication, the app itself has not been updated and the info can sometimes be pretty outdated and it will take several seconds to correct itself, so for example my complication said the temp was 65, but when I opened the app it said it was 53 and didn't update until I force-pressed and told it to refresh.
It's not exactly clear if there are 2 separate events for the dock and complication, or if they're just combined into the same pool if you have the app in both. I'm guessing the latter.
I'm not sure exactly what's going on with the snapshot not updating - it was working 100% fine during the watchOS beta, but the GM seems to have broken something somewhere. Looking into it.
Updated to latest beta this morning. Morning Report arrived at correct time. However Large Slot only showing Current rather than Location for over an hour despite a couple of syncs. App itself was showing correct Location.
No Precipitation Alerts as yet despite heavy thunderstorms overhead in the UK. One question - is Synchronisation only required following changes to Complications settings?
No Precipitation Alerts as yet despite heavy thunderstorms overhead in the UK. One question - is Synchronisation only required following changes to Complications settings?
Precipitation alerts won't show up if you open the app and it's either already raining or is about to start raining.
And yes, you only have to sync when you update your complication settings. That button doesn't do anything else.
i don't seem to be getting any kind of morning or evening reports, even though they're set up in the app. i'm in China... any link? what should they look like?
Are you on the beta? I found a bug that's preventing them from being delivered for some users, so that's probably why you haven't received them. Got a fix into the beta last night.