Seems like the article mentions that it only affects 64-bit devices.I agree that MOST would never set the date to earlier than 1970 and would not be affected by this bug.
But there are scam artists out there that dupe people into doing this to uncover a hidden gem.
This article explains it better. It affects all IOS devices i believe.
http://www.neowin.net/news/apple-acknowledges-1970-bug-that-bricks-64-bit-ios-devices-fix-on-the-way
Apple should fix this problem, but it won't stop jilted lovers or nerdy bullies from doing bad things to your phone. If they can't brick the phone, they can still drop a brick on it.You wouldn't but perhaps a techy jilted lover or nerdy bully would do this to your phone…? Don't laugh, they're out there.
I think Maps was a bullet for the gun.
Cook made the decision to go live with an app that was not ready
I really don't trust Cook. I have a much higher opinion of Forstall. I am a shareholder so obviously not pleased with Cook's performance.
I'm more unhappy from the end user standpoint. I loved Apple products pre-Cook. Now my purchases are much less frequent. A significant part of my buying decision is will it be fun or another headache? Before Cook was CEO my budget was the only limiting factor when contemplating a purchase.
You're joking, right? It's a UNIX issue. Other UNIX based OSs would have had this exact bug at some point. Though it was just now discovered in this current version of iOS, they probably had this issue for a while.
I believe it does as well and I edited my original post to reflect that.Seems like the article mentions that it only affects 64-bit devices.
In any case, some people have also tried to rope users in with various graphics claiming that setting the date to January 1, 1970 will unlock an Easter Egg within iOS and set a "classic Macintosh theme". Although this bug won't do anything on non-64-bit chip iOS devices, anything from an iPhone 5S to the most recent 6s Plus, as well as all iPads starting with the original Air, and recent gen iPod touch will get "bricked" if you apply one of the problematic dates. In terms of operating systems, the flaw has reportedly been confirmed on all versions of iOS from 8.0 up to 9.3.
Why would anyone set their date so far back?
Because things were so much better back in 1970.
Good point about the NTP server. I hadn't thought of that. Wow, someone could make a "free wifi" network that bricks every iPhone that joins it!Speaking as a programmer, one of my jobs is to ensure users cannot either accidentally or deliberately enter values that break the systems I develop. I would in fact say that checking and validating user input is probably the most time consuming part of development as you have to anticipate and mitigate so many different scenarios.
So while it is clear this bug takes quite a lot of effort to trigger it is Apple's fault for not protecting against it, especially since it can brick your device. If someone else gets hold of your iDevice and manually changes the time or if someone spoofs an NTP server and sends your device a fake time it shouldn't result in a broken device. The system should detect an valid value and reset to a safe default.
Initially people were duped into doing it being told that doing so would replace the current Apple logo on the startup screen with a retro rainbow Apple logo. So of course they would set the date to Jan. 1, 1970 and then they had to shut down and reboot in order for the changes to take effect. Once they reboot it was too late and the phone gets bricked.why would anyone set their phone to the wrong date?
I find it funny that we continue to have such large issues related to something that seems as benign as the date/time of a computer. I think back to all of the hullabaloo around Y2K. Just curious and a little amusing to me.
https://www.reddit.com/r/jailbreak/comments/458ao3/discussion_changing_time_date_settings_to_jan_1/Why are people blaming Apple? First of all there is NO reason for anyone to be setting their date that far back. It makes no sense to do so. I don't think a fix is necessary as common sense says don't set the date to Jan. 1, 1970 and the other half of your brain should be questioning why do it in the first place. That said if a fix was needed then why not just make Jan. 1, 1971 the oldest date or even Jan 2, 1970. That way no one could ever set it to Jan. 1, 1970 if they even wanted to.
Not responding to the problem ASAP. This time bug had been going on for a long time...and now they just responding with a fix?Wrong. Under Settings > Date & Time, simply set "Set Automatically" to On.
With respect to fixing the bug, it has been acknowledged and will be pushed out soon in an update. So when you say "incapable," what are you talking about?
I don't think Apple would put such an app on my phone. But I would blame my friend first, and I would trust that friend less. It's not the kind of thing a real friend does.I think your crazy.
Firstly, why should anyone have to start providing reasons to Apple, the point is it happened. If they changed the rules to 'Free repairs for those who can come up with convincing stories' would that keep you happy?
Secondly, the point is, its not fixed now, its still happening to people now, it could happen to people who don't even change the settings via man-in-the-middle network attacks
Finally, your throwing a brick at comment is pointless. This is a FLAW with Apple software and THEY alone are responsible for it, the bug can occur through normal use of the phone. People always love a joke, others don't know what their doing. Put it this way, if you had an app on your home screen put there by Apple and it said DO NOT OPEN, and opening it bricked the device, would you blame Apple if a friend of yours opened the app?
No. HELL no. You did this to your phone by your own volition. You knew from the beginning that it would brick your iPhone but you went ahead and did it anyway. This is totally on the ignorant, stupid users who went and did it just to see what would happen. It would be the same truth if this had been an Android phone. Stupid is as stupid does.
The issue has just been recently discovered and they are addressing it in the next update they are going to release...what's the point again?Not responding to the problem ASAP. This time bug had been going on for a long time...and now they just responding with a fix?
why would anyone set their phone to the wrong date?
Probably the same reason that people set their clocks to the wrong time. It might be some weird placebo effect that comes from it.
I find it funny that you refer to this as a “large issue.” This is a bug that has gone unnoticed for years until some OCD type figured it out accidentally. It’s a SELF INFLICTED bug that is easily avoided. Simply don’t do it! But the stupid ones did it anyway and you call it a major issue?
O
It doesn't really matter, a setting easily available in the UI shouldn't be able to cause this kind of problem.