Maybe I'm in the minority, but ever since iCloud backup for our phones, my iphone hasn't connected to itunes. I don't have apps backed up there. So I guess there's no roll back option for me. [haven't updated or tested the app.]
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.
Growing Number of Users Report Crashing Issue with Latest Nest for iOS Update [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
Wait. Now Apple has to do QA for other companies too? Shouldn't Google/Nest make sure that their own app works on devices before submitting it?
Somewhat on topic, but does anyone else feel Apple needs to take a release cycle and just fine tune iOS 8? I mean there's a laundry list of issues in the iOS subforum on MacRumors with little things like Reminders not syncing among others.
HobeSoundDarryl
macrumors G5
Is that like the spite or stupidity of iOS 8.0.1 where Apple had plenty of time to test that thing? Or- let me guess- that was completely different.
Yeah?!? Google didnt update their OS to 8.1 Apple did.
----------
Apple updated their OS and not Google. Think about it!
HobeSoundDarryl
macrumors G5
You have to be joking or did you miss this: https://www.macrumors.com/2014/09/24/ios-8-0-1-issues-possible-fix/
Consider adding the wink emoti to your joke. Or go visit that thread if you were not joking.
Apple does review updates. I'm pretty sure any update gets the full slate of automated tests, or at least nearly so. My impression is that they tailor the manual review to the release notes provided by the developer, though it wouldn't surprise me if they sanity checked those. (When submitting an update you are asked to describe what has changed to the reviewers. You might say, "fixed a typo in the instructions" or "major redesigned and rewrite of all functions!" and it will get different treatment.)
But of course Apple will start the app on any submission.
The problem is that existing user state/content is most likely to cause a bug like this. That's why, e.g., deleting the app and reinstalling it often fixes this kind of bug. Deleting the app also deletes local user-specific data associated with the app. That's also what helps these kinds of bugs slip through. Even the developers don't always anticipate all the different cases for changes to historical user data. And Apple would not even begin to be able to tackle that.
So this is 100% on Nest. But I'm sure they'll figure it out and release a bug fix soon. They do not seem to have the greatest QA though.
That was probably overeagerness to roll out. File under stupidity I suppose.
This underscores the importance of ALL software/firmware updates being OPT-IN instead of forced or automatic.
Granted, these problems are with Nest's iOS App. And it's easy to make your iOS App updates OPT-IN only (by manually picking and choosing which ones to update). But Nest is about to send out a firmware update to ALL Nest thermostats in customer's homes. Nest generated an email about it about a week ago. The update will be AUTOMATIC. The customer is now allowed to OPT-OUT. Well, the customer CAN OPT-OUT by disconnecting his Nest from his WiFi network, but that disconnect would have to be permanent and then you'd lose a bunch of features.
I've been complaining over on Nest's community forum because I don't want Nest to update the firmware on my Nest. I don't want the new features, I don't want the new menu system, I don't want my Nest changed in any way.
Well, that's not true... If Nest would release a firmware update that caused the thermostat to shut off the A/C (or heat) when the SET temperature is reached, THAT would be an updated I love to have. But, no, Nest INSISTS on running the A/C (or heat) for a full degree to degree and a half BEYOND the set temperature.
Example: Nest is set to 73 degrees. A/C comes on when temperature gets to 74 degrees. A/C runs until Nest shows temperature of 72 degrees. That's a two degree spread when I SET IT for 73 degrees!
But it's actually worse than that. The Nest has a range within each temp setting. So, if I set it to the middle of the 73 degree range (73.5), it doesn't kick on until it gets to the END of the 74 degree range (74.9?) and runs the A/C until it's at the BEGINNING of the 72 degree range (72.1?). So, the spread (72.1 to 74.9) is actually closer to a THREE degree range!
Very very annoying! Every previous digital thermostat I've owned didn't have a range. If you set it to 73 the A/C would kick on the moment it indicated 74 degrees and shut off the moment it indicated 73 degrees again.
Nest's "green" features may work for some people, but they are annoying as all get out for retired folks like my wife and me. It was a HUGE mistake for us to spend the $249 on a Nest. For us, the company has become the epitome of "don't give a crap what the customer thinks, we know best"!
All they have to do is give us the OPTION to set the range ourselves. Give us the OPTION to prevent firmware updates. Give the customer a CHOICE!
Mark
Granted, these problems are with Nest's iOS App. And it's easy to make your iOS App updates OPT-IN only (by manually picking and choosing which ones to update). But Nest is about to send out a firmware update to ALL Nest thermostats in customer's homes. Nest generated an email about it about a week ago. The update will be AUTOMATIC. The customer is now allowed to OPT-OUT. Well, the customer CAN OPT-OUT by disconnecting his Nest from his WiFi network, but that disconnect would have to be permanent and then you'd lose a bunch of features.
I've been complaining over on Nest's community forum because I don't want Nest to update the firmware on my Nest. I don't want the new features, I don't want the new menu system, I don't want my Nest changed in any way.
Well, that's not true... If Nest would release a firmware update that caused the thermostat to shut off the A/C (or heat) when the SET temperature is reached, THAT would be an updated I love to have. But, no, Nest INSISTS on running the A/C (or heat) for a full degree to degree and a half BEYOND the set temperature.
Example: Nest is set to 73 degrees. A/C comes on when temperature gets to 74 degrees. A/C runs until Nest shows temperature of 72 degrees. That's a two degree spread when I SET IT for 73 degrees!
But it's actually worse than that. The Nest has a range within each temp setting. So, if I set it to the middle of the 73 degree range (73.5), it doesn't kick on until it gets to the END of the 74 degree range (74.9?) and runs the A/C until it's at the BEGINNING of the 72 degree range (72.1?). So, the spread (72.1 to 74.9) is actually closer to a THREE degree range!
Very very annoying! Every previous digital thermostat I've owned didn't have a range. If you set it to 73 the A/C would kick on the moment it indicated 74 degrees and shut off the moment it indicated 73 degrees again.
Nest's "green" features may work for some people, but they are annoying as all get out for retired folks like my wife and me. It was a HUGE mistake for us to spend the $249 on a Nest. For us, the company has become the epitome of "don't give a crap what the customer thinks, we know best"!
All they have to do is give us the OPTION to set the range ourselves. Give us the OPTION to prevent firmware updates. Give the customer a CHOICE!
Mark
I bought this because of the energy savings features but the iPhone app has been a nice extra... For example, on my way home from vacation I've been able to turn it off of Auto Away mode an hour or 2 away from the house to start getting the house warmer/cooler for us. If you think your Honeywell (or whatever brand you're using) thermostat is just as good you're wrong - the features in this thermostat are fantastic. I've literally noticed a dramatic decrease in our bills.
A clueless take on this. Nest was crap the whole time- their smoke detectors had to be pulled off the market and their reviews are pretty bad. And unlike Apple, their software bugs don't get fixed quickly. As for Beats, people are still saying they're crap, because they are. You are the only one here who changes based on what Apple says.Oh brother!Go back and look at Nest threads before they were acquired by Google. We praised the product, even hoped Apple might buy them. Then Google buys them. The product doesn't change at all. But now it's garbage.
Meanwhile, go back and look at Beats threads before they were acquired by Apple. We bashed Beats to no end even as rumors started piling up that Apple might be buying Beats. Then Apple does buy them. The product doesn't change. But now it's becoming some of the best headphones available.
What does that say about us?
Correct. We are quick to overlook or forget when Apple rolls out a release that breaks the core functionality of our phones but we'll find fault with stuff like this that really has no consequence and is easily rolled back to a prior software version to address the problem for anyone who desperately needs to use this particular app right now.
Again, what does that say about us?
Now that Nest is owned by Google, was this really a surprise?
Google. Where everything is a beta. Forever.
The delivery content network only affected 40,000 users that's hardly broken. If you got The full file it worked perfectly. you guys are being ridiculous with the sensationalism
Oh brother!
Meanwhile, go back and look at Beats threads before they were acquired by Apple. We bashed Beats to no end even as rumors started piling up that Apple might be buying Beats. Then Apple does buy them. The product doesn't change. But now it's becoming some of the best headphones available.
What does that say about us?
You do realize most of the people that hated Beats before still does, right? Same for Nest. Most that liked/hated it before feel the same as before. You just read comments and opinions of multiple people. It isn't the usually the same people just changing what they think based on who owns the company.