I'm in the UK, and my car trip today was on major roads/motorways with a mixture of 3G/4G, passing some major towns and cities, but not through them. I saw some locations that I hadn't seen before on an identical, earlier trip.
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
Do me a favour, come round for coffee and see if yours shows the same "&" I'm getting?
All jokes aside, happy yours is performing correctly.
As you know, there's sections of our main motorway system that still has next to no signal let alone 3G/4G.
Might take up the offer of coffee one day 
My route was M1 in the Midlands to M18 then A1M to Northumberland and back.
Not total success, as the dreaded ampersand has appeared now on my home location.
My route was M1 in the Midlands to M18 then A1M to Northumberland and back.
Not total success, as the dreaded ampersand has appeared now on my home location.
My app location data has been updating very quickly while driving today from town to town. But I have noticed that the displayed information on my current forecast can't fit on the screen. Is this normal? Can't the app just shorten the forecast when it won't fit? Doesn't look as streamlined this way. Also, the "lt snow" looks like it snow instead of light snow. Any way the app can be better at abbreviating forecasts like this so it looks better? Maybe "light snow soon" would've fit better than trying to fit whatever longer sentence it was trying to say. If I tapped on the complication and opened the app, it just said party sunny with the temp lol. No mention of snow other than the graph.
well the release notes for the newest Watch OS 2.2 Beta 3 stated that the Test Flight issue was resolved BUT I am still unable to install the Carrot Beta...... :*(
My app location data has been updating very quickly while driving today from town to town. But I have noticed that the displayed information on my current forecast can't fit on the screen. Is this normal? Can't the app just shorten the forecast when it won't fit? Doesn't look as streamlined this way. Also, the "lt snow" looks like it snow instead of light snow. Any way the app can be better at abbreviating forecasts like this so it looks better? Maybe "light snow soon" would've fit better than trying to fit whatever longer sentence it was trying to say. If I tapped on the complication and opened the app, it just said party sunny with the temp lol. No mention of snow other than the graph.
I think to... is tonight. The graph looks like about midnight so I wouldn't say 7 hours is "soon".
Replacing under with < would probably have done the trick.
Oh im sure the "to..." meant tonight. I just think it would be cleaner for the app to abbreviate forecasts specifically on the complication, given its small allotted space.
I don't see snow where I am, but I also think I don't get the same level of detail in my forecasts when it comes to precipitation. Dark sky need to expand their more detailed data to China. Lol
I agree. I guess light and under 1" are kind of saying the same thing too. Snow (under 1") or light snow almost certainly mean the same thing. Would you get light snow (over 1")? What becomes non light snow.
"Light snow" is an indication of rate of snow fall. "Under 1 inch" is an indication of accumulation. They don't necessarily have any relation to eachother and neither is an direct indication of the other.
Example: you can have one inch of heavy snow or one inch of light snow. Different rates, same accumulation.
If I was due to have light snow later tonight, accumulating around one inch, I would rather the complication say "under 1" snow later" or "Light snow tonight, >1" or just "light snow later" or something to that effect. Not something long and drawn out that won't fit on the screen.
You can't have 1" of heavy snow, because it's not enough to be defined as heavy by any meteorological institution - even if it fell in a 5 second period.
But I do agree. I'm sure it's another quirk of the forecast.io data (like my double conditions) and it'll get filtered
Ok so what am I doing wrong? Bought the app and the premium features, go to settings and go under complications but nothing happens on the watch.. It only says Carrot5
When I click on the carrot5 it gives me a spinning /loading circle and then nothing happens ..
Help!
When I click on the carrot5 it gives me a spinning /loading circle and then nothing happens ..
Help!
Always worth a power cycle if there's an installation issue - hold down digital crown and side button until the Apple logo appears. Or try removing and reinstalling.
Been getting a lot more "Current" and &'s on this beta as opposed to the last one. This is my current screen, even after a refresh/update, it stayed as "Current"
Hmm, I haven't been getting the usual email notifications that there were new posts in this thread, so sorry I missed all these!
I just posted a new beta seed that should start to round up some more of the location issues. You'll still see some ampersands and asterisks in the location names, but continue to let me know if those show up (and how frequently you're seeing them).
This is just due to the fact that the Watch app was written during the summer/fall, so I didn't have all these winter conditions to test against and filter for shorter messages. In the version I just pushed out, I switched "lt snow" to "l. snow" and "(under 1")" to "(<1"). I'll probably get rid of the light/heavy designations completely in the next seed since they just take up so much room and it's not really clear what they mean when abbreviated unless you take a second to think about it.
This is a bug in watchOS that’s affecting a small number of users who try to install apps that have been updated for watchOS 2. Curiously enough, installing the app via a TestFlight beta fixes everything and stops the app from crashing. I'll PM you about getting you invited to the beta.
I just posted a new beta seed that should start to round up some more of the location issues. You'll still see some ampersands and asterisks in the location names, but continue to let me know if those show up (and how frequently you're seeing them).
This is just due to the fact that the Watch app was written during the summer/fall, so I didn't have all these winter conditions to test against and filter for shorter messages. In the version I just pushed out, I switched "lt snow" to "l. snow" and "(under 1")" to "(<1"). I'll probably get rid of the light/heavy designations completely in the next seed since they just take up so much room and it's not really clear what they mean when abbreviated unless you take a second to think about it.
This is a bug in watchOS that’s affecting a small number of users who try to install apps that have been updated for watchOS 2. Curiously enough, installing the app via a TestFlight beta fixes everything and stops the app from crashing. I'll PM you about getting you invited to the beta.
I shhould have updated my post, i sent an email to support on the app and was invited to do the beta testing. I was able to install it and it is now working! hopefully this gets updated in the future i was a minute away from giving up
awesome!!!! very glad to hear this. keep up the good work. it makes me feel better knowing we pay good money for all the app versions, and the subscription and that you as the dev is very open to feedback and keep up with updates.
If you're in a location that uses Fahrenheit, it'll automatically default to that on first install of the app. Just go into the iPhone app and toggle the temperature setting to Fahrenheit then back to Celsius, then open the main Apple Watch app to force the change to sync over. The data might be cached on the Watch so the change may not take effect right away, but the next time it updates it should be in Celsius.
Can you try opening the iPhone app to load the weather on there, then open the main Watch app, then let me know if this shows up again? (It probably won't update the complication right away, so don't worry if it doesn't fix itself immediately.) I think this is showing up because I started caching the location name, but didn't put in a check to make sure there actually was a location name in the cache before trying to display it.
Went to dinner before and the watch switched to the town I was in. Once I got home, it I guess attempted to switch but gave me the name of the town over and an &. Sat like that for about 4 hours until I did a manual refresh which then fixed it. The screen shot shows just before and then after the refresh with the correct info displayed. On a side note, snow starting in about 3 hours vs starting in 6 mins proves it was displaying cached info and not fresh stuff right? That about coincides with how long it was since my last attempted fetch of the new location (getting home)
Is the cache stored in the watch or the phone?
I'd opened the phone app after updating but before it managed to install the update on the watch (I noticed it said Current Loc*tion above the smaller "current location", before it found my current location) but haven't opened it since.
The error has, however, gone now of its own accord