{"id":71886,"date":"2017-12-03T19:34:19","date_gmt":"2017-12-03T17:34:19","guid":{"rendered":"https:\/\/ngradio.gr\/?p=71886\/"},"modified":"2017-12-03T19:34:19","modified_gmt":"2017-12-03T17:34:19","slug":"apples-shockingly-bad-week-software-problems","status":"publish","type":"post","link":"https:\/\/ngradio.gr\/en\/news-el\/technology-en\/apples-shockingly-bad-week-software-problems\/","title":{"rendered":"Apple’s had a shockingly bad week of software problems"},"content":{"rendered":"

As the week draws to a close, it\u2019s definitely been a long one for Apple\u2019s software engineers. The nightmare started on Tuesday, after a Twitter user disclosed a\u00a0critical security vulnerability for macOS High Sierra<\/a>\u00a0that allowed anyone with physical access to a Mac to gain system administrator privileges without even entering a password. As software bugs go, this one was embarrassing and critical, but Apple\u00a0managed to fix it<\/a>\u00a0less than 24 hours after it was publicly disclosed.<\/p>\n

\u201cSecurity is a top priority for every Apple product, and regrettably we stumbled with this release of macOS,\u201d admitted an Apple spokesperson. \u201cWe greatly regret this error and we apologize to all Mac users, both for releasing with this vulnerability and for the concern it has caused. Our customers deserve better. We are auditing our development processes to help prevent this from happening again.\u201d<\/p>\n

As the auditing of development processes begins, other issues have come to light on the macOS side as a result of this software fix. Apple\u2019s security update ended up introducing a problem preventing Mac users from authenticating or connecting to file shares on their Macs. Apple was forced to issue yet another\u00a0support document<\/a>\u00a0to detail a fix for these users, helping Mac owners gain access to file shares again.<\/p>\n

That seemed to be an embarrassing end to the problems, but late last night reports emerged that Apple\u2019s rushed software patch could be just as buggy as the code it was supposed to fix.\u00a0Wired<\/em>\u2019s Andy Greenberg reports<\/a>\u00a0that multiple Mac users who had not yet upgraded their operating system from the original version of High Sierra to the new 10.13.1 update, but installed Apple\u2019s patch, are seeing the root problem reoccur after they install the latest macOS system update. Reinstalling Apple\u2019s separate patch hasn\u2019t helped these users, unless they reboot and then install it. It\u2019s a shoddy example of Apple rushing to fix a critical issue and not taking the time to test it properly.<\/p>\n

\"iPhone<\/span><\/span><\/figure>\n

 <\/p>\n

Mac users have had a confusing week, but some iPhone users didn\u2019t escape unscathed. An\u00a0iOS 11 bug started crashing some iPhones<\/a>after the clocks hit 12:15AM this morning. Apple has had a\u00a0history<\/a>\u00a0of strange\u00a0time-related bugs<\/a>\u00a0affecting iOS\u00a0multiple times<\/a>\u00a0over the years, but this particular issue appears to be related to recurring notifications for apps like reminders. After issuing a final developer beta of iOS 11.2 to developers last night, Apple decided to take the highly unusual step of\u00a0issuing iOS 11.2 to all iPhone owners to fix the crashing\u00a0<\/a>issues today.<\/p>\n

Apple generally issues iOS updates on a Tuesday at 1PM ET \/ 10AM PT, but this bug has clearly made the company push its release a lot earlier than it was potentially planning. iOS 11.2 also includes a fix for a new autocorrect issue where the word “it” would be\u00a0autocorrected to “I.T\u201d automatically<\/a>. Apple fixed a similar\u00a0autocorrect bug with iOS 11.1.1<\/a>after the operating system had been automatically changing the letter \u201cI\u201d to \u201cA [?]\u201d for some users.<\/p>\n

Let\u2019s recap the week of Apple software problems:<\/p>\n