Content deleted Content added
Loganscott74 (talk | contribs) m Removed random period and added a short description |
No edit summary |
||
| (44 intermediate revisions by 23 users not shown) | |||
Line 1:
{{Short description|
{{Use American English|date=October 2021}}
{{Use mdy dates|date=July 2020}}
{{Update|date=
{{More citations needed|date=January 2024}}
The [[iOS]] mobile operating system developed by [[Apple Inc.|Apple]] has had a wide range of [[Software bug|bugs]] and security issues discovered throughout its lifespan, including security exploits discovered in most versions of the operating system related to the practice of [[iOS jailbreaking|jailbreaking]] (to remove Apple's software restrictions), bypassing the user's [[lock screen]] (known as lock screen bypasses), issues relating to battery drain, crash bugs encountered when sending photos or certain [[Unicode]] characters via text messages sent through the [[Messages (Apple)|Messages]] application, and general bugs and security issues later fixed in newer versions of the operating system.<!-- The lead needs expansion. You can help by adding to it. -->
Line 10:
=== Alarm clock bugs ===
Users reported bugs in the Alarm functionality of the Clock app in all versions of iOS 4. The first bug noticed was the "DST bug" which was first seen when some countries switched to/from daylight saving time from/to standard time in October or November 2010.<ref name="SMH iOS 4 alarm bug">{{cite web |url=https://www.smh.com.au/digital-life/iphone/apple-to-fix-dst-alarm-bug-20101007-168um.html |title=Apple to fix DST alarm bug |date=October 7, 2010 |website=The Sydney Morning Herald |access-date=September 19, 2012 |archive-date=April 6, 2011 |archive-url=https://web.archive.org/web/20110406070138/http://www.smh.com.au/digital-life/iphone/apple-to-fix-dst-alarm-bug-20101007-168um.html |url-status=live }}</ref><ref name="Engadget iOS 4 DST alarm fail">{{cite web|url=https://www.engadget.com/2010/11/01/iphone-dst-bug-causing-alarms-to-fail-across-europe|title=iPhone DST bug causing alarms to fail across Europe (updated)|date=November 1, 2010|website=Engadget|access-date=January 8, 2012|archive-date=November 22, 2011|archive-url=https://web.archive.org/web/20111122182730/http://www.engadget.com/2010/11/01/iphone-dst-bug-causing-alarms-to-fail-across-europe/|url-status=live}}</ref> It caused recurring alarms to
The second alarm clock bug discovered was the "New Year's Day bug" which showed up on January 1, 2011 and January 1, 2012. It caused non-recurring alarms to never work.<ref name="Engadget iOS 4 alarm bug">{{cite web|url=https://www.engadget.com/2010/12/31/psa-iphone-alarms-not-working-come-new-years-day-2011|title=PSA: iPhone alarms not working come New Year's Day 2011|date=December 31, 2010|website=Engadget|access-date=January 8, 2012|archive-date=January 8, 2012|archive-url=https://web.archive.org/web/20120108033011/http://www.engadget.com/2010/12/31/psa-iphone-alarms-not-working-come-new-years-day-2011|url-status=live}}</ref> However, two days after each New Year's Day, on January 3, 2011, the bug appeared to resolve itself. This bug was seemingly fixed in iOS 4.3.<ref name="Engadget iOS 4 alarm again">{{cite web|url=https://www.engadget.com/2012/01/01/psa-iphone-alarm-clock-not-working-again-time-to-update|title=PSA: iPhone alarm clock not working again? Time to update|date=January 1, 2012|website=Engadget|access-date=January 8, 2012|archive-date=January 8, 2012|archive-url=https://web.archive.org/web/20120108013333/http://www.engadget.com/2012/01/01/psa-iphone-alarm-clock-not-working-again-time-to-update|url-status=live}}</ref>
Line 18:
=== Battery drain bugs ===
Apple confirmed that several battery life bugs were negatively affecting battery life in iOS 5.<ref name="Engadget iOS 5 battery bug">{{cite web|url=https://www.engadget.com/2011/11/02/apple-confirms-ios-5-bugs-causing-battery-drain-promises-a-fix|title=Apple confirms iOS 5 bugs causing battery drain, promises a fix 'in a few weeks'|date=November 2, 2011|website=Engadget|access-date=January 17, 2012|archive-date=January 7, 2012|archive-url=https://web.archive.org/web/20120107105142/http://www.engadget.com/2011/11/02/apple-confirms-ios-5-bugs-causing-battery-drain-promises-a-fix/|url-status=live}}</ref>
=== Wi-Fi ===
The launch of the iOS 5 update on October 12, 2011 (including iOS 5.0.1 released on November 10, 2011), led many users to report a major bug causing the device to lose [[Wi-Fi]] access. This problem
=== SIM card ===
Line 27:
=== Echo bugs ===
Some users of the iPhone 4 and iPhone 4S reported issues with having echo problems during phone call in the initial release of iOS 5, which
== iOS 6 ==
Line 34:
=== Maps ===
{{Main article|Apple Maps#Early inaccuracy (2012)}}
Apple admitted that there were several bugs in the mapping app on [[iOS 6]], with cities in the wrong ___location, some places
=== Bluetooth ===
Line 70:
=== Motion sickness ===
Users complained about motion sickness-like symptoms when using iOS 7 because of the user interface's animation and parallax effects. In iOS 7.1, a new function in the Settings app named "Reduce Motion" was introduced to reduce the motion of the user interface and disable the parallax effects.<ref>{{cite news|title=How Apple's iOS 7.1 finally quelled users' motion sickness|author=Craig Grannell|newspaper=The Guardian|date=March 13, 2014|url=https://www.theguardian.com/technology/2014/mar/13/apple-iphone-ipad-ios-71-motion-sickness|access-date=July 15, 2020|archive-date=July 16, 2020|archive-url=https://web.archive.org/web/20200716151335/https://www.theguardian.com/technology/2014/mar/13/apple-iphone-ipad-ios-71-motion-sickness|url-status=live}}</ref>▼
▲In iOS 7.1, a new function in the Settings app named "Reduce Motion" was introduced to reduce the motion of the user interface and disable the parallax effects.<ref>{{cite news|title=How Apple's iOS 7.1 finally quelled users' motion sickness|author=Craig Grannell|newspaper=The Guardian|date=March 13, 2014|url=https://www.theguardian.com/technology/2014/mar/13/apple-iphone-ipad-ios-71-motion-sickness|access-date=July 15, 2020|archive-date=July 16, 2020|archive-url=https://web.archive.org/web/20200716151335/https://www.theguardian.com/technology/2014/mar/13/apple-iphone-ipad-ios-71-motion-sickness|url-status=live}}</ref>
=== Creation of CardDAV Accounts not working ===
Line 104 ⟶ 103:
=== Touch ID ===
Users who updated phones with Touch ID enabled to iOS 8.3 found out that they could not use Touch ID to make App Store purchases.<ref>{{cite web|url=http://wccftech.com/apple-released-ios-83-bug-fixes-features/|title=Touch ID Fails in App Store With Apples Recent iOS 8.3 Release|date=April 9, 2015|newspaper=WCCFTech|access-date=April 12, 2015|archive-date=April 15, 2015|archive-url=https://web.archive.org/web/20150415070407/http://wccftech.com/apple-released-ios-83-bug-fixes-features/|url-status=live}}</ref> A workaround
=== Performance ===
Line 113 ⟶ 112:
=== iMessage ===
When a specific sequence of Arabic, Unicode, and English characters
== iOS 9 ==
Line 131 ⟶ 130:
=== 9.7-inch iPad Pro bricking issue ===
iOS 9.3.2 caused problems for some 9.7-inch iPad Pro owners, with multiple ''MacRumors'' readers and Twitter users reporting issues shortly after installing the update over the air. Affected users
As a result, iOS 9.3.2 update was withdrawn.<ref>{{Cite web |last=Mayo |first=Benjamin |date=2016-05-20 |title=Apple pulls iOS 9.3.2 for 9.7 inch iPad Pro following reports of bricked devices with 'Error 56' issue |url=https://9to5mac.com/2016/05/20/apple-pulls-ios-9-3-2-for-9-7-inch-ipad-pro-following-reports-of-bricked-devices-with-error-56-issue/ |access-date=2022-03-22 |website=9to5Mac |language=en-US |archive-date=March 22, 2022 |archive-url=https://web.archive.org/web/20220322014159/https://9to5mac.com/2016/05/20/apple-pulls-ios-9-3-2-for-9-7-inch-ipad-pro-following-reports-of-bricked-devices-with-error-56-issue/ |url-status=live }}</ref> This issue was fixed with a re-release version of iOS 9.3.2 in June 2016, with build number 13F72.<ref>{{Cite web |last=Cunningham |first=Andrew |date=2016-06-02 |title=After bricking saga, Apple re-posts iOS 9.3.2 update for 9.7-inch iPad Pro [Updated] |url=https://arstechnica.com/gadgets/2016/06/apple-pulls-ios-9-3-2-update-for-9-7-inch-ipad-pro-after-reports-of-bricking/ |access-date=2022-03-22 |website=Ars Technica |language=en-us |archive-date=March 22, 2022 |archive-url=https://web.archive.org/web/20220322014147/https://arstechnica.com/gadgets/2016/06/apple-pulls-ios-9-3-2-update-for-9-7-inch-ipad-pro-after-reports-of-bricking/ |url-status=live }}</ref>
Line 137 ⟶ 136:
=== iPhone 4S lawsuit ===
{{See also|Batterygate}}
Apple faced a lawsuit alleging its iOS 9 mobile operating software significantly slowed down the iPhone 4S. The lawsuit
=== Bluetooth ===
Line 149 ⟶ 148:
=== Recovery mode issues ===
The initial iOS 10 update released on September 13, 2016,
As a result, the initial release was pre-installed only on [[iPhone 7]] and [[iPhone 7]] Plus. Apple released iOS 10.0.1 shortly afterwards, and issued an apology.<ref>{{Cite web |date=2016-09-13 |title=iOS 10 Update Error Causes 'Plug into iTunes', Fix Requires iTunes [u] {{!}} iPhone in Canada Blog |url=https://www.iphoneincanada.ca/news/ios-10-recovery-mode-fix/ |access-date=2022-03-23 |language=en-US |archive-date=January 19, 2022 |archive-url=https://web.archive.org/web/20220119082106/https://www.iphoneincanada.ca/news/ios-10-recovery-mode-fix/ |url-status=live }}</ref>
=== "30% battery bug" ===
Many users, especially those owning an iPhone 6s, reported that their phones would shut down automatically with 30% battery left.<ref>{{cite web|url=http://clark.com/technology/iphone-battery-drain-apple-bug/|title=Mysterious bug is still shutting down iPhones with 30% battery left|date=January 25, 2017|work=Clark Howard|access-date=October 28, 2017|archive-date=October 29, 2017|archive-url=https://web.archive.org/web/20171029064937/http://clark.com/technology/iphone-battery-drain-apple-bug/|url-status=live}}</ref> This issue was fixed with the release of iOS 10.3. As of the iOS 10.2.1 release, iOS
=== Crash caused by 5-second video ===
On November 22, 2016, a
== iOS 11 ==
Line 166 ⟶ 165:
=== Mail ===
Users with Outlook.com, Office 365, and certain [[Microsoft Exchange Server|Exchange]] accounts were unable to send email.<ref>{{cite web|url=https://support.apple.com/en-us/HT208136|title=If you can't send an email with iOS 11 and an Outlook.com or Exchange mail account|work=Apple Support|access-date=September 25, 2017|archive-date=September 26, 2017|archive-url=https://web.archive.org/web/20170926182313/https://support.apple.com/en-us/HT208136|url-status=live}}</ref> This
=== AutoCorrect ===
Line 172 ⟶ 171:
=== December 2 respring ===
A bug in iOS 11 was present that would cause the device's home screen to constantly crash if an app
=== Telugu character crash ===
Line 185 ⟶ 184:
=== Group FaceTime bug ===
{{main|FaceTime#Group FaceTime bug}}
A privacy issue was discovered when using [[FaceTime]] in iOS 12.1
=== Sending iMessages to the wrong contacts ===
iOS 12
=== iOS 12.3.2 update incompatibility ===
Line 197 ⟶ 196:
== iOS 13 ==
=== Battery drain issues ===
Some users reported excessive battery drain following the initial release of iOS 13. IOS 13.1.1 fixed the problem.<ref>{{cite news|last=Clover|first=Juli|date=September 27, 2019|title=Apple Releases iOS and iPadOS 13.1.1 With Siri and Battery Drain Fix, Keyboard Vulnerability Update and More|website=[[MacRumors]]|url=https://www.macrumors.com/2019/09/27/apple-releases-ios-13-1-1/|url-status=live|access-date=September 27, 2019|archive-url=https://web.archive.org/web/20191207070732/https://www.macrumors.com/2019/09/27/apple-releases-ios-13-1-1/|archive-date=December 7, 2019}}</ref>
=== Memory management issue ===
Line 202 ⟶ 204:
=== HomePod bricking issue ===
According to multiple people on the MacRumors forums and Reddit, the 13.2 update "bricked" their HomePods, rendering them unusable. Users who
=== iOS 13.5 jailbreak ===
Line 213 ⟶ 215:
=== Default app setting reset ===
The ability to change the default app for messages, email, web browsing, or other services
=== General battery drain ===
On September 30, 2020, Apple acknowledged a battery drain issue in iOS 14 and released a supporting document that offered the users tricks to fix the poor battery performance. In this document Apple claimed that unpairing the iPhone from an Apple Watch followed by erasing all data and settings of the iPhone, and restoring from a backup could be a possible fix for the battery life.<ref>{{cite web|url=https://www.theverge.com/2020/10/2/21499243/ios-14-watchos-7-battery-drain-apple-iphone-watch-fix|title=If iOS 14 is causing battery drain, you might need to wipe your iPhone|access-date=2 October 2020|website=The Verge|date=October 2, 2020 |archive-date=October 5, 2020|archive-url=https://web.archive.org/web/20201005183545/https://www.theverge.com/2020/10/2/21499243/ios-14-watchos-7-battery-drain-apple-iphone-watch-fix|url-status=live}}</ref>
== iOS 15 ==
== iOS 16 ==
=== Image capture issues ===
On iOS 16.0, a bug
=== Activation issues ===
Line 230 ⟶ 234:
=== Copy and paste alerts ===
Some iOS 16 users
=== Mail lockout ===
An Apple Mail bug caused a specifically crafted address in the "from" field to lock users out of Apple Mail on versions prior to iOS 16.0.3. This bug only
=== Camera app slowdowns ===
Line 239 ⟶ 243:
=== Missing notifications ===
Some users
=== CarPlay microphone issues ===
Prior to iOS 16.0.3, some CarPlay users
=== WiFi issues ===
Some users
=== iPhone 14 Pro series "horizontal lines" issue ===
In December 2022, reports
=== Messages and Photos vulnerabilities ===
Line 254 ⟶ 258:
=== Storage issues ===
Some users reported that storage took over their space on iOS 16.4. When they tried to clear storage,
=== Weather app issues ===
Some users
=== Screen Time issues ===
Some users
== iOS 17 ==
=== iPhone 15 Pro thermal issues ===
=== NFC issues on iPhone 15 Pro (BMW owner only) ===
A specific and concerning issue arose where some iPhone 15 Pro/Pro Max owners experienced NFC chip failure, which impacted functionalities like Apple Pay and digital car keys, after wirelessly charging their device on certain BMW in-car charging pads. Affected users reported their iPhone entering a data recovery mode with a white screen, and upon reboot, the NFC chip would no longer function, often displaying a "Could Not Set Up Apple Pay" error message. Initially, some customers received replacement iPhones from Apple, but these replacement devices were also susceptible to the same issue when used with the problematic BMW chargers, indicating a broader compatibility or design flaw rather than isolated device defects.<ref>{{Cite web |date=2023-10-01 |title=Warning: BMW Wireless Charging May Break iPhone 15's Apple Pay Chip |url=https://www.macrumors.com/2023/10/01/bmw-charging-may-break-iphone-15-nfc-chip/ |url-status=live |archive-url=https://web.archive.org/web/20231001135919/https://www.macrumors.com/2023/10/01/bmw-charging-may-break-iphone-15-nfc-chip/ |archive-date=2023-10-01 |access-date=2023-10-01 |website=MacRumors |language=en}}</ref>
Apple attempted to address this issue with the iOS 17.1.1 and 17.2 updates. User reports after these updates were mixed but generally indicated improvement. Some users confirmed that the iOS 17.1.1 update fixed the problem, with their NFC functionality remaining intact even if the phone still experienced temporary overheating during wireless charging in the car. This suggests that while the underlying thermal load from some BMW wireless chargers might persist, Apple's software updates managed to prevent the NFC chip from failing permanently. The issue appears to have been a complex interaction between the phone's thermal management, the wireless charging pad's heat output, and the NFC chip's sensitivity, which Apple largely mitigated through software adjustments.<ref>{{Cite web |last=Miller |first=Chance |date=5 December 2023 |title=Apple says iOS 17.2 fixes iPhone wireless charging problems in 'certain vehicles' |url=https://9to5mac.com/2023/12/05/iphone-wireless-charging-gm-ios-17/ |website=9to5Mac}}</ref>
=== iPhone 15 series display image persistence ===
=== Shutdown issues ===
Some users reported that their iPhones turned off temporarily at night, interrupting alarms and other iPhone features. This
=== App switcher appears while typing ===
A hard-to-replicate bug
=== iOS 17.3 beta 2 boot loop ===
An issue with iOS 17.3 beta 2 caused devices to be in a constant boot loop after installing the beta, primarily affecting the iPhone 12–15 series phones. As a result, the beta was pulled three hours after release. According to some reports, this issue
=== Text auto-completion issues ===
=== Photos reappearing ===
Line 287 ⟶ 297:
== iOS 18 ==
== iOS 26 ==
== See also ==
* [[iPhone OS 3|Issues relating to iPhone OS]]
== References ==
| |||