Maker of carrot. How do I get a beta invite?
I just installed the watchOS 3 beta and my Carrot app is going crazy! I have it set as the middle complication in the modular face but when I click on the complication or when I try to go to it through the dock the app goes crazy. Basically it's just quickly cycling through all the little graphics that show when you force touch to update the app. This happens no matter how I access the app (through the complication, through the dock, or through the icon on the honeycomb app screen). Is this a bug or just something weird going on with my watch? Help!
This exact thing happen to me yesterday with carrot... then it just froze with no movement. First time ever that I had a problem with Carrot and I blame that on beta code for the watch. I rebooted the watch and all has been fine ever since.I've heard of one other user experiencing this issue so far, though it's working fine for others. Not really sure what the issue is yet as I haven't been able to poke around in watchOS 3, hopefully it's something small that I can fix in the watchOS 2 version so I can get an update out before the official launch.
If you reboot the watch, does the issue persist?
This exact thing happen to me yesterday with carrot... then it just froze with no movement. First time ever that I had a problem with Carrot and I blame that on beta code for the watch. I rebooted the watch and all has been fine ever since.
Carrot - I am hearing that you will have more control over the complications with watchOS3 - is that true? Any clue what you might do?Yeah, Apple betas can often completely break third-party apps, either because of bugs in the beta or because they changed something behind the scenes that requires an update of the third-party app. The last few major betas have been pretty good in this regard, perhaps because they've opened the beta program up to the public so they're being more careful in the releases.
Carrot - I am hearing that you will have more control over the complications with watchOS3 - is that true? Any clue what you might do?
Also, has Apple made any changes to the frequency of updates?
What else do you notice with watchOS3 that you can take advantage of? Too early?
I don't think there have been any new public releases for a while. The major changes are in the betas. Worth signing up for the beta programme.
Alright I guess I need to be part of this program.
Carrot, how do I get signed up ? Tks.
Ok tks, email sent !Submit a request by tapping the big green button at the bottom of the iOS app's settings screen!
Just pushed out an update with some iOS 10 fixes as well as the new backend for subscriptions. Going to finally put this live on the App Store in the next few weeks so I can get started on iOS 10 / watchOS 3 stuff in earnest.
Your (and all other) widgets now size properly on iOS 10 b2. Just thought I'd let you know if you didn't already
I'm still having delayed or failed location information on the modular complication with watch beta 3 and iOS 10. Never happened on 2.2.1 or iOS 9.3.3 betas. I find that I will have to update the app on the watch manually and even then, the old location persists for awhile before changing over to my correct one.
Settings from before weren't changed. Location info is set to always and background refresh is turned on. Anyone else noticing very slow (1+ hour) to update location data.
Edit: the newest Carrot beta on watchOS 3 beta 2 just force closes when you try to refresh it. Tried reinstalling on the watch with no luck.
Edit 2: the app works now and can update fine however the complication refuses to load. It shows the dashes (-------) and even though there is updated weather info, the complication won't update.
Other weather apps show the info, so I don't think watchOS or the complication is the issue.
Never received an email notification for this post, sorry for the delayed response!
There are a lot of big changes in watchOS 3 to the way complications and apps work, so I'm sure that's the culprit here. I've been getting reports from other watchOS 3 users saying that everything either works 100% fine, or only sporadically, or not at all - and that's definitely to be expected with a beta that changes so much stuff.
The current plan is to finish up the current beta and put that out in the next week or so, then get started on iOS 10 and watchOS 3 stuff. (Will very likely be making the app iOS 10 and watchOS 3 only at launch to take full advantage of all the new stuff.)
How is it possible if the app is manually updated, the complication doesn't reflect that immediately. I think maybe you addressed that before but I forget. Only a set amount of updates can be done an hour?