Issues relating to iOS: Difference between revisions

Content deleted Content added
Citation bot (talk | contribs)
Alter: template type. | You can use this bot yourself. Report bugs here. | Suggested by AManWithNoPlan | All pages linked from cached copy of User:AManWithNoPlan/sandbox3 | via #UCB_webform_linked 159/687
No edit summary
 
(219 intermediate revisions by 82 users not shown)
Line 1:
{{Short description|none}}
{{Use American English|date=October 2021}}
{{Use mdy dates|date=July 2020}}
{{Update|date=December 2024|reason=coverage is missing on issues related to versions before [[iOS 4]], [[iOS 15]], [[iOS 18]], and [[iOS 26]]}}
{{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. -->
 
== iOS 4 ==
The [[iOS]] mobile operating system developed by [[Apple Inc.]] has had a wide range of bugs and security issues discovered throughout its lifespan, ranging from security exploits discovered in most versions of the operating system related to the practice of [[iOS jailbreaking|jailbreaking]], as well as bypassing the user's lock screen (known as lock screen bypasses), to issues relating to battery drain, to 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.
{{main|iOS 4#Problems}}{{Expand section|date=February 2024}}
 
=== IssuesAlarm byclock iOS versionbugs ===
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 go off an hour too early or too late. Apple promised the bug would be fixed in iOS 4.2, but according to some reports it still existed in iOS 4.3.1.<ref name="Softpedia iOS 4 alarm bug">{{cite web|url=http://news.softpedia.com/news/iOS-4-3-1-Patch-Imperative-Battery-Drain-Alarm-Clock-Bug-Safari-Hole-189466.shtml|title=iOS 4.3.1 Patch Imperative – Battery drain, Alarm Clock bug, Safari hole|date=March 14, 2011|website=Softpedia|access-date=January 8, 2012|archive-date=February 9, 2012|archive-url=https://web.archive.org/web/20120209130206/http://news.softpedia.com/news/iOS-4-3-1-Patch-Imperative-Battery-Drain-Alarm-Clock-Bug-Safari-Hole-189466.shtml|url-status=live}}</ref>
 
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>
=== iOS 4 ===
{{main|iOS 4#Problems}}
; Alarm clock bugs
The Alarm feature of the built in Clock app in the iPhone and iPod Touch has been plagued by major bugs 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 |accessdate=September 19, 2012}}</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|accessdate=January 8, 2012}}</ref> It caused recurring alarms to start going off an hour too early or late. Apple promised the bug would be fixed in iOS 4.2/4.2.1 but according to some reports it still exists even in iOS 4.3.1.<ref name="Softpedia iOS 4 alarm bug">{{cite web|url=http://news.softpedia.com/news/iOS-4-3-1-Patch-Imperative-Battery-Drain-Alarm-Clock-Bug-Safari-Hole-189466.shtml |title=iOS 4.3.1 Patch Imperative – Battery drain, Alarm Clock bug, Safari hole|date=March 14, 2011|website=Softpedia|accessdate=January 8, 2012}}</ref>
 
== iOS 5 ==
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|accessdate=January 8, 2012}}</ref> However, two days after each New Year's Day, on January 3, 2011, they "magically" started working again. 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|accessdate=January 8, 2012}}</ref>
 
=== iOS 5 ===
{{main|iOS 5#Problems}}
; 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|accessdate=January 17, 2012}}</ref> They attempted to fix these bugs with iOS 5.0.1 and 5.1 but the problem still remained.<ref name="Engadget iOS 5 battery improvement">{{cite web|url=https://www.engadget.com/2011/11/11/poll-have-you-noticed-battery-improvements-after-updating-to-io |title=Poll: Have you noticed battery improvements after updating to iOS 5.0.1?|date=November 11, 2011|website=Engadget|accessdate=January 8, 2012}}</ref> Finally, these bugs were fixed in iOS 5.1.1.
;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 has supposedly been fixed with the release of iOS 5.1.1<ref name="Engadget iOS 5 wifi bug">{{cite web|url=https://www.engadget.com/2011/11/21/thanks-to-ios-5-some-users-lose-wifi-connectivity |title=Thanks to iOS 5.1 some users lose Wifi connectivity|date=November 21, 2011|website=Engadget|accessdate=January 13, 2012}}</ref><ref name="Simonblog wifi bug">{{cite web|url=http://www.simonblog.com/2011/11/27/wi-fi-connectivity-problems-with-ios-5-update |title=Wi-Fi connectivity problems with iOS 5.1 update|date=November 27, 2011|website=Simonblog|accessdate=January 8, 2012|archive-url=https://web.archive.org/web/20140224013700/http://www.simonblog.com/2011/11/27/wi-fi-connectivity-problems-with-ios-5-update/|archive-date=February 24, 2014|url-status=dead}}</ref>
;SIM card
Some users of the iPhone 4S and iPad (Wi-Fi + Cellular) reported issues with the [[Subscriber Identity Module|SIM]] card in iOS 5.0,<ref name="AppleInsider SIM bug">{{cite web|url=https://www.appleinsider.com/articles/11/11/17/users_report_sim_card_issues_with_apples_iphone_4s_and_ios_5_0_1.html |title=Users report SIM card issues with Apple's iPhone 4S and iOS 5.0.1|date=November 17, 2011|accessdate=}}</ref> and even though Apple attempted to fix these issues in version 5.0.1 build 9A406 (for iPhone 4S only), they still remained.<ref name="AppleInsider SIM bug remain">{{cite web|url=https://www.appleinsider.com/articles/11/12/16/new_ios_build_meant_to_fix_iphone_4s_sim_card_issues.html |title=New iOS build meant to fix iPhone 4S SIM card issues|author=AppleInsider Staff|date=December 16, 2011|accessdate=}}</ref>
;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 causes echoes to appear randomly during phone calls made through earbuds. The other party in the call is generally unable to hear the conversation due to this problem.<ref>{{cite web|url=http://www.bgr.com/2011/11/01/audio-echo-bug-plagues-iphone-4s-owners-during-voice-calls/ |title=Audio echo bug plagues iPhone 4S owners during voice calls|author=|date=November 1, 2011|website=BGR|accessdate=March 21, 2013}}</ref> Apple has since released version 5.1.1 in an attempt to fix the problem.
 
=== iOSBattery 6drain 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> Apple attempted to fix these bugs with iOS 5.0.1 and 5.1 but the problem still remained.<ref name="Engadget iOS 5 battery improvement">{{cite web|url=https://www.engadget.com/2011/11/11/poll-have-you-noticed-battery-improvements-after-updating-to-io|title=Poll: Have you noticed battery improvements after updating to iOS 5.0.1?|date=November 11, 2011|website=Engadget|access-date=January 8, 2012|archive-date=January 7, 2012|archive-url=https://web.archive.org/web/20120107140530/http://www.engadget.com/2011/11/11/poll-have-you-noticed-battery-improvements-after-updating-to-io|url-status=live}}</ref> All of these bugs were fixed in iOS 5.1.1.{{citation needed|date=November 2024}}
 
=== 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 was supposedly fixed with the release of iOS 5.1.1.<ref name="Engadget iOS 5 wifi bug">{{cite web|url=https://www.engadget.com/2011/11/21/thanks-to-ios-5-some-users-lose-wifi-connectivity|title=Thanks to iOS 5.1 some users lose Wifi connectivity|date=November 21, 2011|website=Engadget|access-date=January 13, 2012|archive-date=January 27, 2012|archive-url=https://web.archive.org/web/20120127094400/http://www.engadget.com/2011/11/21/thanks-to-ios-5-some-users-lose-wifi-connectivity/|url-status=live}}</ref><ref name="Simonblog wifi bug">{{cite web|url=http://www.simonblog.com/2011/11/27/wi-fi-connectivity-problems-with-ios-5-update |title=Wi-Fi connectivity problems with iOS 5.1 update|date=November 27, 2011|website=Simonblog|access-date=January 8, 2012|archive-url=https://web.archive.org/web/20140224013700/http://www.simonblog.com/2011/11/27/wi-fi-connectivity-problems-with-ios-5-update/|archive-date=February 24, 2014|url-status=dead}}</ref>
 
=== SIM card ===
Some users of the iPhone 4S and iPad (Wi-Fi + Cellular) reported issues with the [[Subscriber Identity Module|SIM]] card in iOS 5.0,<ref name="AppleInsider SIM bug">{{cite web|url=https://www.appleinsider.com/articles/11/11/17/users_report_sim_card_issues_with_apples_iphone_4s_and_ios_5_0_1.html|title=Users report SIM card issues with Apple's iPhone 4S and iOS 5.0.1|date=November 17, 2011|access-date=July 15, 2020|archive-date=July 15, 2020|archive-url=https://web.archive.org/web/20200715212228/https://appleinsider.com/articles/11/11/17/users_report_sim_card_issues_with_apples_iphone_4s_and_ios_5_0_1.html|url-status=live}}</ref> and even though Apple attempted to fix these issues in version 5.0.1 build 9A406 (for iPhone 4S only), they still remained.<ref name="AppleInsider SIM bug remain">{{cite web|url=https://www.appleinsider.com/articles/11/12/16/new_ios_build_meant_to_fix_iphone_4s_sim_card_issues.html|title=New iOS build meant to fix iPhone 4S SIM card issues|author=AppleInsider Staff|date=December 16, 2011|access-date=July 15, 2020|archive-date=July 15, 2020|archive-url=https://web.archive.org/web/20200715214752/https://appleinsider.com/articles/11/12/16/new_ios_build_meant_to_fix_iphone_4s_sim_card_issues.html|url-status=live}}</ref>
 
=== 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 caused echoes to appear randomly during phone calls made through earbuds. The other party in the call was generally unable to hear the conversation due to this problem.<ref>{{cite web|url=http://www.bgr.com/2011/11/01/audio-echo-bug-plagues-iphone-4s-owners-during-voice-calls/|title=Audio echo bug plagues iPhone 4S owners during voice calls|date=November 1, 2011|website=BGR|access-date=March 21, 2013|archive-date=June 9, 2013|archive-url=https://web.archive.org/web/20130609173042/http://bgr.com/2011/11/01/audio-echo-bug-plagues-iphone-4s-owners-during-voice-calls/|url-status=live}}</ref> Apple released version 5.1.1 in an attempt to fix the problem.
 
== iOS 6 ==
{{main|iOS 6#Problems}}
 
;Maps
=== Maps ===
Apple has admitted that there were several bugs in the mapping app on [[iOS 6]], with cities in the wrong ___location, some places being missed off altogether, some places misnamed and places of interest in the sea.<ref name="Letter from Tim Cook on Maps">{{cite web|url=https://www.apple.com/letter-from-tim-cook-on-maps |title=Letter from Tim Cook on Maps|archive-url=https://web.archive.org/web/20121001014531/http://www.apple.com/letter-from-tim-cook-on-maps|archive-date=October 1, 2012}}</ref><ref name="compweekly map errors">{{cite web|url=http://www.computerweekly.com/news/2240163685/Apple-admits-iPhone-5-Maps-app-needs-fixing |title=Apple admits iPhone 5 Maps app needs fixing|accessdate=September 21, 2012}}</ref><ref name="ibtimes map errors">{{cite web|url=http://www.ibtimes.com/apple-concedes-its-errors-maps-application-asserts-working-hard-improve-experience-expert-rules-out |title=Apple Concedes Its Errors in Maps Application; Asserts 'Working Hard' To Improve Experience; Expert Rules Out Google Maps App For iOS 6|website=IBT|accessdate=September 21, 2012}}</ref> Problems submitted by users have gradually been addressed with daily updates to Maps.<ref>{{cite web|url=https://appleinsider.com/articles/14/06/30/apple-updating-its-maps-with-user-corrections-every-day-at-3-am-eastern |title=Apple updating its Maps with user corrections every day at 3&nbsp;am Eastern|accessdate=April 19, 2015}}</ref>
{{Main article|Apple Maps#Early inaccuracy (2012)}}
;Bluetooth
Apple admitted that there were several bugs in the mapping app on [[iOS 6]], with cities in the wrong ___location, some places missing altogether, some places misnamed, and some places of interest in the sea.<ref name="Letter from Tim Cook on Maps">{{cite web|url=https://www.apple.com/letter-from-tim-cook-on-maps |title=Letter from Tim Cook on Maps|archive-url=https://web.archive.org/web/20121001014531/http://www.apple.com/letter-from-tim-cook-on-maps|archive-date=October 1, 2012}}</ref><ref name="compweekly map errors">{{cite web|url=http://www.computerweekly.com/news/2240163685/Apple-admits-iPhone-5-Maps-app-needs-fixing|title=Apple admits iPhone 5 Maps app needs fixing|access-date=September 21, 2012|archive-date=September 24, 2012|archive-url=https://web.archive.org/web/20120924013117/http://www.computerweekly.com/news/2240163685/Apple-admits-iPhone-5-Maps-app-needs-fixing|url-status=live}}</ref><ref name="ibtimes map errors">{{cite web|url=http://www.ibtimes.com/apple-concedes-its-errors-maps-application-asserts-working-hard-improve-experience-expert-rules-out|title=Apple Concedes Its Errors in Maps Application; Asserts 'Working Hard' To Improve Experience; Expert Rules Out Google Maps App For iOS 6|website=IBT|date=September 21, 2012 |access-date=September 21, 2012|archive-date=September 23, 2012|archive-url=https://web.archive.org/web/20120923163711/http://www.ibtimes.com/apple-concedes-its-errors-maps-application-asserts-working-hard-improve-experience-expert-rules-out|url-status=live}}</ref> Problems submitted by users were gradually addressed with daily updates to Maps.<ref>{{cite web|url=https://appleinsider.com/articles/14/06/30/apple-updating-its-maps-with-user-corrections-every-day-at-3-am-eastern|title=Apple updating its Maps with user corrections every day at 3&nbsp;am Eastern|date=June 30, 2014 |access-date=April 19, 2015|archive-date=April 20, 2015|archive-url=https://web.archive.org/web/20150420030343/http://appleinsider.com/articles/14/06/30/apple-updating-its-maps-with-user-corrections-every-day-at-3-am-eastern|url-status=live}}</ref>
Many users report a problem with Bluetooth audio streaming to a range of compatible devices. The sound cuts out every now and then for no apparent reason. {{As of|2012|10}}, no solution has been provided by Apple.<ref>{{cite web|url=https://discussions.apple.com/thread/4318307?start=0&tstart=0 |title=iOS 6 Bluetooth problems}}</ref>
 
;Location-based Reminders
=== Bluetooth ===
Location-based reminders do not work for iPads, even though they were promised to work on cellular enabled devices.<ref>{{cite web|url=https://discussions.apple.com/thread/4311603 |title=Will Location based reminders work on ios 6 for the IPad 3 I keep getting a message that siri can't do ___location based reminders on this device any help please}}</ref> It has later been clarified by Apple that only the 4th generation iPad and the iPad Mini 1st generation or later will be able to use this.<ref>{{cite web|url=https://support.apple.com/en-gb/HT202335 |title=Create and use Reminders on your iPhone and iPad - Apple Support}}</ref>
Many users reported a problem with Bluetooth audio streaming to a range of compatible devices. The sound cut out occasionally for no apparent reason. {{As of|2012|10}}, no solution was provided by Apple.<ref>{{cite web |url=https://discussions.apple.com/thread/4318307?start=0&tstart=0 |title=iOS 6 Bluetooth problems |access-date=July 15, 2020 |archive-date=October 4, 2017 |archive-url=https://web.archive.org/web/20171004035125/https://discussions.apple.com/thread/4318307?start=0&tstart=0 |url-status=live }}</ref>
;Cellular Network
 
In iOS 6.1, users reported problems with cellular connectivity. This was addressed for the iPhone 4S in iOS 6.1.1 which "fixes an issue that could impact cellular performance and reliability for iPhone 4S."<ref name="PCmag 4S bugs">{{cite web|url=https://www.pcmag.com/article2/0,2817,2415311,00.asp |title=Apple Rolls Out iOS 6.1.1 to Fix iPhone 4S Bugs|date=February 11, 2014|work=PC Magazine|accessdate=February 11, 2013}}</ref>
=== Location-based reminders ===
;Do Not Disturb
Location-based reminders did not work for iPads, even though they were promised to work on cellular-enabled devices.<ref>{{cite web |url=https://discussions.apple.com/thread/4311603 |title=Will Location based reminders work on ios 6 for the IPad 3 I keep getting a message that siri can't do ___location based reminders on this device any help please |access-date=July 15, 2020 |archive-date=February 25, 2021 |archive-url=https://web.archive.org/web/20210225062945/https://discussions.apple.com/thread/4311603 |url-status=live }}</ref> It was later clarified by Apple that only the 4th generation iPad and the iPad Mini 1st generation or later would be able to use this.<ref>{{cite web |url=https://support.apple.com/en-gb/HT202335 |title=Create and use Reminders on your iPhone and iPad - Apple Support |access-date=July 15, 2020 |archive-date=March 4, 2016 |archive-url=https://web.archive.org/web/20160304073711/https://support.apple.com/en-gb/HT202335 |url-status=live }}</ref>
Many iPhone users experienced a bug with the Do Not Disturb feature when the calendar changed from 2012 to 2013. The feature would be left on past the scheduled time set by the user, allowing texts, notifications, and alarm settings to be missed. The bug was caused by a difference in formatting in the [[ISO 8601|ISO calendar]] system versus the [[Gregorian calendar]] system.<ref>{{cite web|url=https://arstechnica.com/apple/2013/01/ask-ars-why-will-apples-do-not-disturb-bug-fix-itself-next-week |title=Ask Ars: Why will Apple's Do Not Disturb bug fix itself next week?|date=January 3, 2013|accessdate=January 4, 2013}}</ref> Apple did not offer a quick software update for the bug, instead saying that the bug would fix itself on January 7, 2013.<ref>{{cite web|url=http://support.apple.com/kb/TS4510?viewlocale=en_US&locale=en_US |title=iOS 6: Do Not Disturb mode stays on after scheduled time|date=January 2, 2013|website=Apple.com|accessdate=January 4, 2013}}</ref>
 
;Microsoft Exchange
=== Cellular Network ===
Another bug causes issues when iOS devices connect to a Microsoft Exchange server to retrieve email, resulting in message "mailbox server resources are consumed, log growth becomes excessive, memory and CPU use may increase significantly, and server performance is affected".<ref name="theverge MS Exchange bug">{{cite web|url=https://www.theverge.com/2013/2/12/3981682/microsoft-investigating-ios-6-1-exchange-sync-problems |title=Microsoft suggests throttling or blocking iOS 6.1 devices after bug slows down Exchange servers|date=February 12, 2013|accessdate=February 12, 2013}}</ref> Microsoft have suggested several workarounds,<ref name="MS workarounds for exchange">{{cite web|url=http://support.microsoft.com/kb/2814847 |title=Rapid growth in transaction logs, CPU use, and memory consumption in Exchange Server 2010 when a user syncs a mailbox by using an iOS 6.1-based device|date=February 13, 2013|accessdate=February 13, 2013}}</ref> and Apple responded with a KnowledgeBase article describing the cause of the bug and a suggested temporary workaround, promising a fix in the near future,<ref name="Apple Exchange bug promise">{{cite web|url=http://support.apple.com/kb/TS4532 |title=iOS 6.1: Excess Exchange activity after accepting an exception to recurring calendar event|date=February 13, 2013|accessdate=February 14, 2013}}</ref> which was then fixed with release of iOS 6.1.2.
In iOS 6.1, users reported problems with cellular connectivity. This was addressed for the iPhone 4S in iOS 6.1.1 which "fixes an issue that could impact cellular performance and reliability for iPhone 4S."<ref name="PCmag 4S bugs">{{cite web|url=https://www.pcmag.com/article2/0,2817,2415311,00.asp|title=Apple Rolls Out iOS 6.1.1 to Fix iPhone 4S Bugs|date=February 11, 2014|work=PC Magazine|access-date=February 11, 2013|archive-date=February 14, 2013|archive-url=https://web.archive.org/web/20130214035602/http://www.pcmag.com/article2/0,2817,2415311,00.asp|url-status=live}}</ref>
;Lockscreen bypass code
 
On iPhones, another bug found in 6.1 allowing bypassing the lock screen's passcode to temporarily gain full access to the Phone app, by performing a specific sequence of actions on the phone that remained unfixed,<ref name="Gizmodo 6.1 phone bypass">{{cite web|url=http://www.gizmodo.co.uk/2013/02/you-can-bypass-the-ios-6-1-lockcode-screen-with-this-simple-technique |title=You Can Bypass the iOS 6.1 Lockcode Screen With This Simple Technique|date=February 14, 2013|accessdate=February 14, 2013}}</ref> with Apple acknowledging the bug<ref name="Ars 6.1 bypass fix promise">{{cite web|url=https://arstechnica.com/apple/2013/02/ios-passcode-bug-slated-to-be-fixed-in-ios-6-1-3for-real-this-time |title=iOS passcode bug slated to be fixed in iOS 6.1.3—for real this time|date=February 21, 2013|website=Ars Technica|accessdate=February 26, 2013}}</ref> and then addressed with release of iOS 6.1.3.
=== Do Not Disturb ===
;Audio profile speakerphone
Many iPhone users experienced a bug with the Do Not Disturb feature when the calendar changed from 2012 to 2013. The feature would be left on past the scheduled time set by the user, allowing texts, notifications, and alarm settings to be missed. The bug was caused by a difference in formatting in the [[ISO 8601|ISO calendar]] system versus the [[Gregorian calendar]] system.<ref>{{cite news|url=https://arstechnica.com/apple/2013/01/ask-ars-why-will-apples-do-not-disturb-bug-fix-itself-next-week|title=Ask Ars: Why will Apple's Do Not Disturb bug fix itself next week?|newspaper=Ars Technica |date=January 3, 2013|access-date=January 4, 2013|archive-date=January 4, 2013|archive-url=https://web.archive.org/web/20130104024045/http://arstechnica.com/apple/2013/01/ask-ars-why-will-apples-do-not-disturb-bug-fix-itself-next-week/|url-status=live}}</ref> Apple did not offer a software update, saying that the bug would resolve on January 7, 2013.<ref>{{cite web|url=http://support.apple.com/kb/TS4510?viewlocale=en_US&locale=en_US|title=iOS 6: Do Not Disturb mode stays on after scheduled time|date=January 2, 2013|website=Apple.com|access-date=January 4, 2013|archive-date=January 4, 2013|archive-url=https://web.archive.org/web/20130104190941/http://support.apple.com/kb/TS4510?viewlocale=en_US&locale=en_US|url-status=live}}</ref>
 
=== Microsoft Exchange ===
Another bug caused issues when iOS devices connected to a Microsoft Exchange server to retrieve email, resulting in message "mailbox server resources are consumed, log growth becomes excessive, memory and CPU use may increase significantly, and server performance is affected".<ref name="theverge MS Exchange bug">{{cite web|url=https://www.theverge.com/2013/2/12/3981682/microsoft-investigating-ios-6-1-exchange-sync-problems|title=Microsoft suggests throttling or blocking iOS 6.1 devices after bug slows down Exchange servers|date=February 12, 2013|access-date=February 12, 2013|archive-date=February 15, 2013|archive-url=https://web.archive.org/web/20130215040745/http://www.theverge.com/2013/2/12/3981682/microsoft-investigating-ios-6-1-exchange-sync-problems|url-status=live}}</ref> Microsoft suggested several workarounds;<ref name="MS workarounds for exchange">{{cite web|url=http://support.microsoft.com/kb/2814847|title=Rapid growth in transaction logs, CPU use, and memory consumption in Exchange Server 2010 when a user syncs a mailbox by using an iOS 6.1-based device|date=February 13, 2013|access-date=February 13, 2013|archive-date=February 15, 2013|archive-url=https://web.archive.org/web/20130215043029/http://support.microsoft.com/kb/2814847|url-status=live}}</ref> the bug was fixed with the release of iOS 6.1.2.
 
=== Lockscreen bypass code ===
On iPhones, another bug found in iOS 6.1 allowing bypassing the lock screen's passcode to temporarily gain full access to the Phone app, by performing a specific sequence of actions on the phone. This was fixed with the release of iOS 6.1.3.<ref name="Ars 6.1 bypass fix promise">{{cite web|url=https://arstechnica.com/apple/2013/02/ios-passcode-bug-slated-to-be-fixed-in-ios-6-1-3for-real-this-time|title=iOS passcode bug slated to be fixed in iOS 6.1.3—for real this time|date=February 21, 2013|website=Ars Technica|access-date=February 26, 2013|archive-date=February 25, 2013|archive-url=https://web.archive.org/web/20130225174020/http://arstechnica.com/apple/2013/02/ios-passcode-bug-slated-to-be-fixed-in-ios-6-1-3for-real-this-time/|url-status=live}}</ref>
 
=== Audio profile speakerphone ===
[[iPhone 5]] users experienced dropped calls during the release of iOS 6.1.3 when there was an issue with the audio [[microphone]] profile. This also caused issues with many voice-over commands, including [[Siri]], to get different results than expected or to fail easily. Apple fixed this bug with the release of iOS 6.1.4, which updated the audio speaker profile so users would get better results.
;FaceTime
 
=== FaceTime ===
Shortly after Apple released [[iOS 7]], users running iOS 6 were said to have problems using FaceTime. Apple later released a support document stating that this was due to an expired device certificate and that devices that support iOS 7 should update to it in order to resolve these issues.<ref name="ftbug">{{cite web|url=https://www.macrumors.com/2014/04/24/ios-6-facetime-fix/ |title=iOS 6 Users on Devices Able to Run iOS 7 Must Upgrade to Fix FaceTime|date=April 24, 2014|accessdate=April 19, 2015}}</ref> Devices that are unable to run iOS 7, the fourth-generation [[iPod Touch]] and the [[iPhone 3GS]], should upgrade to iOS 6.1.6.<ref name="ftbug" />
Shortly after Apple released [[iOS 7]], users running iOS 6 were said to have problems using FaceTime. Apple later released a support document stating that this was due to an expired device certificate and that devices that supported iOS 7 should update to it to resolve these issues,<ref name="ftbug">{{cite web|url=https://www.macrumors.com/2014/04/24/ios-6-facetime-fix/|title=iOS 6 Users on Devices Able to Run iOS 7 Must Upgrade to Fix FaceTime|date=April 24, 2014|access-date=April 19, 2015|archive-date=February 4, 2017|archive-url=https://web.archive.org/web/20170204085354/https://www.macrumors.com/2014/04/24/ios-6-facetime-fix/|url-status=live}}</ref> and that devices unable to run iOS 7, the fourth-generation [[iPod Touch]] and the [[iPhone 3GS]], should upgrade to iOS 6.1.6.<ref name="ftbug" />
;Data security
An attacker can collect or modify data in sessions protected by [[SSL/TLS]] protocols. This same bug was also reported on iOS 7.0.4 and iOS 7.0.5 for the iPhone 5C and 5S. For the [[iPhone 3GS]] and the [[iPod Touch (4th generation)]], iOS 6.1.6 was released to fix this issue since iOS 7 is not compatible with these devices (see iOS 7.x).
 
=== iOSData 7security ===
An attacker could collect or modify data in sessions protected by [[SSL/TLS]] protocols. This same bug was also reported on iOS 7.0.4 and iOS 7.0.5 for the iPhone 5C and 5S. For the [[iPhone 3GS]] and the [[iPod Touch (4th generation)]], iOS 6.1.6 was released to fix this issue since iOS 7 is not compatible with these devices. (see iOS 7.x)
 
== iOS 7 ==
{{main|iOS 7#Problems}}
;Passcode screen bypass bugs
People are able to bypass the "Enter Passcode" screen. This flaw was discovered within hours of it becoming publicly available. This is only able to be done on [[iPhone 5]] and earlier while the [[iPhone 5C]] and [[iPhone 5S]] are safe from this bug. This is caused by the ability to use the [[Control Center (iOS)|control center]] via the lock screen and tapping on the camera or timer buttons. This feature can be turned off in the Settings app.<ref>{{cite web|url=https://www.theguardian.com/technology/2013/sep/20/apple-working-fix-ios-7-lockscreen-bypass-flaw |title=Apple says it's working on fix for iOS 7 lockscreen bypass flaw|date=September 20, 2013|website=Guardian News and Media|archiveurl=https://web.archive.org/web/20130920222059/http://www.theguardian.com/technology/2013/sep/20/apple-working-fix-ios-7-lockscreen-bypass-flaw|archivedate=September 20, 2013|url-status=live|accessdate=September 22, 2013|quote=Embarrassing discovery comes within hours of release of new software and exploits Control Center feature to hack into photos, texts and Facebook content}}</ref> This was fixed in iOS 7.0.2.
;Motion Sickness
Users complained about dizziness and vertigo-like symptoms when using this operating system because of parallax motion 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}}</ref>
;Creation of CardDAV Accounts not working
Creating a [[CardDAV]] Account contains a bug that needs manual fixing of the CardDAV-Server-URL.<ref>{{cite web|url=http://help.licobo.com/setting/sync/ios/ios7-carddav/?lang=en |title=licobo.com|accessdate=October 22, 2015}}</ref>
;Battery drain problems
In iOS 7.1, users have reported seeing significant drain on their batteries after installing the new update.<ref>{{cite web|url=https://9to5mac.com/2014/03/13/ios-7-1-makes-everything-faster-including-your-battery-drain/ |title=iOS 7.1 makes everything faster – including your battery drain|work=9to5Mac}}</ref>
;FaceTime
Issues with video-calling and connection errors. This was fixed in iOS 7.0.4. (See iOS 6.x)
;Safari ignores local ___domain
Local ___domain names can no longer be resolved in [[Safari (web browser)|Safari]].<ref>{{cite web|url=https://discussions.apple.com/message/23592318 |title=Safari ignores local ___domain|work=apple.com}}</ref><ref>{{cite web|url=https://discussions.apple.com/thread/5575236 |title=Safari can no longer address <host>.xxyyz... - Apple Support Communities|work=apple.com}}</ref> This breaks short names on the local network, e.g. 'nas' for nas.<ourdomain>.
;Home screen crashes
Users have reported various crashes of the home screen, the core service that renders the home screen icons, Notification Center, Control Center, Siri and the lockscreen.<ref>{{cite web|url=http://crave.cnet.co.uk/mobiles/apple-promises-to-fix-home-screen-crash-iphone-bug-50013288/ |title=Apple promises to fix 'home screen crash' iPhone bug|work=CNET}}</ref> This was fixed in iOS 7.1.
;Data security
Secure transport failed to validate the authenticity of connection. This issue was addressed by restoring missing validation steps. This may cause an attacker with a privileged network position to capture or modify data in sessions protected by [[SSL/TLS]].<ref>{{cite web|url=https://www.macrumors.com/2014/02/21/apple-ios-706/ |title=Apple Releases iOS 7.0.6 With Fix for SSL Connection Verification|work=macrumors.com}}</ref> This issue was addressed by the release of iOS 7.0.6.
;Battery Indicator stuck until restart
[[iPhone 4S]] users report experiencing problems with the battery indicator; the indicator will freeze at the same value until the iPhone is restarted again.<ref>{{cite web|url=https://discussions.apple.com/thread/5331165 |title=iPhone 4S battery indicator stuck after upgrade... - Apple Support Communities|work=apple.com}}</ref><ref>{{cite web|url=https://discussions.apple.com/thread/5104825 |title=battery indicator stuck at 1%|work=apple.com}}</ref>
;Touch ID
In iOS 7.1, [[Touch ID]] was not functioning on the [[iPhone 5S]]. The problem cannot be resolved by turning Touch ID on and off in the "Fingerprint and Passcode" menu, restarting, resetting, or restoring the device using [[iTunes]]. This problem was similar to the [[iOS 8]].0.1 release, which crippled [[iPhone 6|iPhone 6 and iPhone 6 Plus]] of both cellular and Touch ID. This was fixed in iOS 7.1.1.
 
=== iOSPasscode 8screen bypass bugs ===
A lock screen bypass was discovered in 2013 within hours of the release of iOS 7, caused by the ability to use the [[Control Center (iOS)|control center]] through the lock screen and tapping on the camera or timer buttons. The latest iPhone models, the iPhone 5S and the iPhone 5C, were not affected. As a workaround, the Control Center could be turned off for the lock screen in the Settings app.<ref>{{cite web|url=https://www.theguardian.com/technology/2013/sep/20/apple-working-fix-ios-7-lockscreen-bypass-flaw |title=Apple says it's working on fix for iOS 7 lockscreen bypass flaw|date=September 20, 2013|website=Guardian News and Media|archive-url=https://web.archive.org/web/20130920222059/http://www.theguardian.com/technology/2013/sep/20/apple-working-fix-ios-7-lockscreen-bypass-flaw|archive-date=September 20, 2013|url-status=live|access-date=September 22, 2013|quote=Embarrassing discovery comes within hours of release of new software and exploits Control Center feature to hack into photos, texts and Facebook content}}</ref> This was fixed in iOS 7.0.2.<ref>{{Cite web|last=Gurman|first=Mark|date=2013-09-26|title=Apple releases iOS 7.0.2 with fix for Lock screen passcode bypass flaw|url=https://9to5mac.com/2013/09/26/apple-releases-ios-7-0-2-with-lock-screen-passcode-flaw-fix/|access-date=2021-01-30|website=9to5Mac|language=en-US|archive-date=February 10, 2021|archive-url=https://web.archive.org/web/20210210125743/https://9to5mac.com/2013/09/26/apple-releases-ios-7-0-2-with-lock-screen-passcode-flaw-fix/|url-status=live}}</ref>
 
=== 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>
 
=== Creation of CardDAV Accounts not working ===
Creating a [[CardDAV]] Account had a bug that required manual fixing of the CardDAV-Server-URL.<ref>{{cite web|url=http://help.licobo.com/setting/sync/ios/ios7-carddav/?lang=en|title=licobo.com|access-date=October 22, 2015|archive-date=March 5, 2016|archive-url=https://web.archive.org/web/20160305224149/http://help.licobo.com/setting/sync/ios/ios7-carddav?lang=en|url-status=live}}</ref>
 
=== Battery drain problems ===
Users reported seeing significant drain on their devices' battery after installing the update to iOS 7.1.<ref>{{cite web|url=https://9to5mac.com/2014/03/13/ios-7-1-makes-everything-faster-including-your-battery-drain/|title=iOS 7.1 makes everything faster – including your battery drain|work=9to5Mac|access-date=July 15, 2020|archive-date=August 4, 2020|archive-url=https://web.archive.org/web/20200804230215/https://9to5mac.com/2014/03/13/ios-7-1-makes-everything-faster-including-your-battery-drain/|url-status=live}}</ref>
 
=== Safari ignores local ___domain ===
Local ___domain names could no longer be resolved in [[Safari (web browser)|Safari]],<ref>{{cite web|url=https://discussions.apple.com/message/23592318|title=Safari ignores local ___domain|work=apple.com|access-date=July 15, 2020|archive-date=August 6, 2018|archive-url=https://web.archive.org/web/20180806145601/https://discussions.apple.com/message/23592318|url-status=dead}}</ref><ref>{{cite web|url=https://discussions.apple.com/thread/5575236|title=Safari can no longer address <host>.xxyyz... - Apple Support Communities|work=apple.com|access-date=July 15, 2020|archive-date=February 25, 2021|archive-url=https://web.archive.org/web/20210225063324/https://discussions.apple.com/thread/5575236|url-status=live}}</ref> breaking short names on the local network.
 
=== Home screen crashes ===
Users reported various crashes of the home screen, the core service that renders the home screen icons, Notification Center, Control Center, Siri and the lock screen.<ref>{{cite web|url=https://www.cnet.com/tech/mobile/apple-promises-to-fix-home-screen-crash-iphone-bug/|title=Apple promises to fix 'home screen crash' iPhone bug|work=CNET|date=January 23, 2014|access-date=February 6, 2024}}</ref> This was fixed in iOS 7.1.
 
=== Data security ===
Secure transport failed to validate the authenticity of connection. This issue was addressed by restoring missing validation steps. This could allow an attacker with a privileged network position to capture or modify data in sessions protected by [[SSL/TLS]].<ref>{{cite web|url=https://www.macrumors.com/2014/02/21/apple-ios-706/|title=Apple Releases iOS 7.0.6 With Fix for SSL Connection Verification|work=macrumors.com|date=February 21, 2014 |access-date=July 15, 2020|archive-date=September 24, 2020|archive-url=https://web.archive.org/web/20200924113949/https://www.macrumors.com/2014/02/21/apple-ios-706/|url-status=live}}</ref> This issue was addressed by the release of iOS 7.0.6.
 
=== Battery indicator stuck until restart ===
[[iPhone 4S]] users reported problems with the battery indicator, which would freeze at the same value until the iPhone was restarted.<ref>{{cite web|url=https://discussions.apple.com/thread/5331165|title=iPhone 4S battery indicator stuck after upgrade... - Apple Support Communities|work=apple.com|access-date=July 15, 2020|archive-date=February 26, 2021|archive-url=https://web.archive.org/web/20210226170557/https://discussions.apple.com/thread/5331165|url-status=live}}</ref><ref>{{cite web|url=https://discussions.apple.com/thread/5104825|title=battery indicator stuck at 1%|work=apple.com|access-date=July 15, 2020|archive-date=March 9, 2021|archive-url=https://web.archive.org/web/20210309065530/https://discussions.apple.com/thread/5104825|url-status=live}}</ref>
 
=== Touch ID ===
In iOS 7.1, [[Touch ID]] was not functioning on the [[iPhone 5S]]. The problem could not be resolved by turning Touch ID on and off in the "Fingerprint and Passcode" menu, restarting, resetting, or restoring the device using [[iTunes]].<ref>{{Cite web|last=Prabhu|first=Gautam|date=2014-03-12|title=iPhone 5s users reporting issues with Touch ID after iOS 7.1 update|url=https://www.iphonehacks.com/2014/03/iphone-5s-touch-id-issue-ios-7-1.html|access-date=2021-01-30|website=iPhone Hacks|language=en-US|archive-date=February 5, 2021|archive-url=https://web.archive.org/web/20210205005309/https://www.iphonehacks.com/2014/03/iphone-5s-touch-id-issue-ios-7-1.html|url-status=live}}</ref> This issue was fixed in iOS 7.1.1.<ref>{{Cite web|last=Kingsley-Hughes|first=Adrian|title=Apple releases iOS 7.1.1|url=https://www.zdnet.com/article/apple-releases-ios-7-1-1/|access-date=2021-01-30|website=ZDNet|language=en|archive-date=November 12, 2020|archive-url=https://web.archive.org/web/20201112022134/http://www.zdnet.com/article/apple-releases-ios-7-1-1/|url-status=live}}</ref>
 
== iOS 8 ==
{{main|iOS 8#Problems}}
;HealthKit
Shortly after the release of iOS 8, Apple released a statement pointing out that a bug had been found in the operating system which prevented HealthKit-compatible apps from being released alongside iOS 8.<ref name="HealthKit Bug">{{cite web|url=https://www.cnet.com/news/bug-forces-apple-to-delay-launch-of-healthkit-fitness-apps/ |title=Bug forces Apple to delay launch of HealthKit fitness apps|website=[[CNET]]|archiveurl=https://web.archive.org/web/20141019180636/http://www.cnet.com/news/bug-forces-apple-to-delay-launch-of-healthkit-fitness-apps/|archivedate=October 19, 2014}}</ref> Apps already released that included Healthkit functionality were withdrawn from the App Store. iOS 8.0.1/8.0.2 included a fix for this issue.
;iOS 8.0.1
[[iPhone 6|iPhone 6 and iPhone 6 Plus]] users who updated to iOS 8.0.1 wirelessly had cellular service and Touch ID disabled due to a software issue. Over-the-Air downloads of iOS 8.0.1 were stopped within an hour of the release of the software, but many early adopters had been affected. These issues were fixed with the release of iOS 8.0.2 a day later.
;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}}</ref> A workaround has been devised by users to repair this issue.<ref>{{cite web|url=http://wccftech.com/how-to-fix-touch-id-ios-8-3-bugs/ |title=How to Fix iOS 8.3 Touch ID Issue – iOS 8 Tips and Tricks|date=April 10, 2015|newspaper=WCCFTech|access-date=April 12, 2015}}</ref>
;Performance
Many users of older generation devices such as the iPhone 4s and the iPad 2 reported performance issues with iOS 8. Apple has since released iOS 8.1.1 in attempt to fix the problem.
;Keyboard
Several issues with the new Keyboard API in iOS 8 were reported, including problems with custom keyboards crashing or not appearing, or being replaced with the default keyboard. Apple has since released iOS 8.3 in attempt to fix the problem.
;iMessage
When a specific set of Arabic, Unicode, and English characters are sent through iMessage to an iOS device running iOS 8.0 or later, it causes the device to crash. This bug was discovered by a [[Reddit]] user in May 2015. Apple has since released a software update (iOS 8.4) to fix this issue.<ref>{{cite web|url=http://www.theinquirer.net/inquirer/news/2410183/ios-bug-lets-android-and-windows-phone-users-disable-your-iphones-messages-app |title=iOS 8.4 includes fix for iMessage bug plaguing iPhone users|work=theinquirer.net}}</ref>
 
=== iOS 9HealthKit ===
Shortly after the release of iOS 8, Apple released a statement pointing out that a bug had been found in the operating system which prevented HealthKit-compatible apps from being released alongside iOS 8.<ref name="HealthKit Bug">{{cite web|url=https://www.cnet.com/news/bug-forces-apple-to-delay-launch-of-healthkit-fitness-apps/ |title=Bug forces Apple to delay launch of HealthKit fitness apps|website=[[CNET]]|archive-url=https://web.archive.org/web/20141019180636/http://www.cnet.com/news/bug-forces-apple-to-delay-launch-of-healthkit-fitness-apps/|archive-date=October 19, 2014}}</ref> Apps already released that included HealthKit functionality were withdrawn from the App Store. iOS 8.0.1/8.0.2 included a fix for this issue.
 
=== iPhone 6 cellular issues ===
[[iPhone 6|iPhone 6 and iPhone 6 Plus]] users who updated to iOS 8.0.1 [[Over-the-air update|wirelessly]] had cellular service and Touch ID disabled due to a software issue.<ref>{{Cite web|last=Hall|first=Stephen|date=2014-09-24|title=Apple releases iOS 8.0.1 with fixes, but many users reporting it breaks Cellular + Touch ID|url=https://9to5mac.com/2014/09/24/apple-releases-ios-8-0-1-with-various-improvements-and-bug-fixes/|access-date=2021-01-30|website=9to5Mac|language=en-US|archive-date=July 6, 2016|archive-url=https://web.archive.org/web/20160706233930/http://9to5mac.com/2014/09/24/apple-releases-ios-8-0-1-with-various-improvements-and-bug-fixes/|url-status=live}}</ref> Over-the-air downloads of iOS 8.0.1 were stopped within an hour of the release of the software,<ref>{{Cite web|last=Kingsley-Hughes|first=Adrian|title=Apple pulls iOS 8.0.1 update, after killing cell service, Touch ID|url=https://www.zdnet.com/article/apple-pulls-ios-8-0-1-update-after-killing-cell-service-touch-id/|access-date=2021-01-30|website=ZDNet|language=en|archive-date=April 11, 2021|archive-url=https://web.archive.org/web/20210411224909/https://www.zdnet.com/article/apple-pulls-ios-8-0-1-update-after-killing-cell-service-touch-id/|url-status=live}}</ref> but many early adopters had been affected. These issues were fixed with the release of iOS 8.0.2 a day later.
 
=== 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 was devised by users to repair this issue.{{Unreliable source?|date=January 2024}}<ref>{{cite web|url=http://wccftech.com/how-to-fix-touch-id-ios-8-3-bugs/|title=How to Fix iOS 8.3 Touch ID Issue – iOS 8 Tips and Tricks|date=April 10, 2015|newspaper=WCCFTech|access-date=April 12, 2015|archive-date=April 12, 2015|archive-url=https://web.archive.org/web/20150412093514/http://wccftech.com/how-to-fix-touch-id-ios-8-3-bugs/|url-status=live}}</ref>
 
=== Performance ===
Many users of older generation devices such as the iPhone 4S and the iPad 2 reported performance issues with iOS 8. iOS 8.1.1 addressed the problem.<ref>{{Cite web|last=Cunningham|first=Andrew|date=2014-11-04|title=iOS 8.1.1 said to address iPhone 4S and iPad 2 performance problems|url=https://arstechnica.com/gadgets/2014/11/ios-8-1-1-said-to-address-iphone-4s-and-ipad-2-performance-problems/|access-date=2021-01-30|website=Ars Technica|language=en-us|archive-date=February 5, 2021|archive-url=https://web.archive.org/web/20210205090239/https://arstechnica.com/gadgets/2014/11/ios-8-1-1-said-to-address-iphone-4s-and-ipad-2-performance-problems/|url-status=live}}</ref>
 
=== Keyboard ===
Several issues with the new Keyboard API in iOS 8 were reported, including problems with custom keyboards crashing or not appearing, or being replaced with the default keyboard.{{Citation needed|date=January 2021}} iOS 8.3 addressed the problem.
 
=== iMessage ===
When a specific sequence of Arabic, Unicode, and English characters were sent through iMessage to a device running iOS 8.0 through iOS 8.3, it caused the device to crash and restart; if the Messages app was then opened, the crash repeated.<ref>{{cite news| last=Page | first=Carly | title=iMessage bug can bork the Apple Watch, Macs and iPads too |publisher=The Inquirer| date=28 May 2015 | url=http://www.theinquirer.net/inquirer/news/2410183/ios-bug-lets-android-and-windows-phone-users-disable-your-iphones-messages-app | archive-url=https://web.archive.org/web/20150529002053/http://www.theinquirer.net/inquirer/news/2410183/ios-bug-lets-android-and-windows-phone-users-disable-your-iphones-messages-app | archive-date=29 May 2015 | url-status=dead}}</ref> This bug, which had existed since iOS 6 but had previously had little impact, was reported by a [[Reddit]] user in May 2015 and prompted a lot of such messages to be sent deliberately. This issue was resolved in iOS 8.4, released on July 1, 2015.<ref>{{cite news| last=Erwin | first=Derek | title=iOS 8.4 Update Fixes Text Message Bug Causing iPhones to Restart | website=The Mac Security Blog | date=1 July 2015 | url=https://www.intego.com/mac-security-blog/ios-8-4-update-fixes-text-message-bug-iphone-restart/}}</ref>
 
== iOS 9 ==
{{main|iOS 9#Problems}}
;Game Center
 
=== Game Center ===
Many users reported greatly increased [[Game Center]] loading times which in turn caused apps that used Game Center logins to appear to load slowly.<ref>{{cite web|url=https://www.cultofmac.com/390755/beware-this-fix-for-nasty-ios-9-game-center-bug/ |title=Beware this 'fix' for nasty iOS 9 Game Center bug|website=Cult of Mac|accessdate=October 21, 2015}}</ref> This was fixed in iOS 9.1.
Many users reported greatly increased [[Game Center]] loading times which in turn caused apps that used Game Center logins to appear to load slowly.<ref>{{cite web|url=https://www.cultofmac.com/390755/beware-this-fix-for-nasty-ios-9-game-center-bug/|title=Beware this 'fix' for nasty iOS 9 Game Center bug|website=Cult of Mac|date=September 30, 2015 |access-date=October 21, 2015|archive-date=October 21, 2015|archive-url=https://web.archive.org/web/20151021134645/http://www.cultofmac.com/390755/beware-this-fix-for-nasty-ios-9-game-center-bug/|url-status=live}}</ref> This was fixed with the release of iOS 9.1.
 
;=== January 1, 1970 ===
On 64-bit iOS devices, setting the date to January 1, 1970 and restarting the iPhone would prevent the device from starting up until it lost power or its time setting shifted past January 1, 1970.<ref>{{cite web|url=https://gizmodo.com/what-the-hell-is-going-on-with-this-1970-iphone-bug-1759242670|title=What the Hell Is Going on With This 1970 iPhone Bug?|work=Gizmodo|date=February 16, 2016 |access-date=October 28, 2017|archive-date=October 29, 2017|archive-url=https://web.archive.org/web/20171029065108/https://gizmodo.com/what-the-hell-is-going-on-with-this-1970-iphone-bug-1759242670|url-status=live}}</ref> This was fixed with the release of iOS 9.3.
 
=== Error 53 ===
On 64-bit iOS devices, setting the date to January 1, 1970 and restarting the iPhone would prevent the device from starting up until it lost power or its time setting shifted past January 1, 1970.<ref>{{cite web|url=https://gizmodo.com/what-the-hell-is-going-on-with-this-1970-iphone-bug-1759242670 |title=What the Hell Is Going on With This 1970 iPhone Bug?|work=Gizmodo|access-date=October 28, 2017}}</ref> This was fixed with the release of iOS 9.3.
Updating an iPhone 6 with a replaced Touch ID sensor to a new version of iOS would cause the update to fail and report an "Error 53.",<ref name="iOS 9.2.1 error 53 fix">{{cite web|url=https://www.cultofmac.com/413066/apple-apologizes-for-error-53-releases-fix/|title=Apple apologizes for Error 53, releases fix {{!}} Cult of Mac|date=February 18, 2016|work=Cult of Mac|access-date=October 28, 2017|archive-date=October 29, 2017|archive-url=https://web.archive.org/web/20171029013502/https://www.cultofmac.com/413066/apple-apologizes-for-error-53-releases-fix/|url-status=live}}</ref> as a result of additional hardware security checks left unintentionally.<ref name="iOS 9.2.1 error 53 fix"/> This was fixed with a re-release of iOS 9.2.1, with build number 13D20.
 
;=== Error 53 Lawsuit ===
Apple faced a lawsuit filed February 11, 2016<ref>{{Cite web |title=PCVA Files Class Action Lawsuit Apple Error 53 Issue |url=https://www.pcva.law/press-releases/pcva-files-class-action-lawsuit-apple-error-53-issue/ |access-date=2023-02-24 |website=Pfau Cochran Vertetis Amala PLLC |language=en-US}}</ref><ref>{{Cite web |title=Apple Facing Class Action Lawsuit Over 'Error 53' iPhone 6 Bricking |url=https://www.macrumors.com/2016/02/11/apple-facing-error-53-class-action-lawsuit/ |access-date=2023-02-24 |website=MacRumors |date=February 11, 2016 |language=en}}</ref><ref>{{Cite news |last=Brignall |first=Miles |date=2016-02-12 |title=Seattle law firm files first lawsuit against Apple over iPhone 'error 53' |language=en-GB |work=The Guardian |url=https://www.theguardian.com/technology/2016/feb/12/seattle-law-firm-files-first-lawsuit-against-apple-over-iphone-error-53 |access-date=2023-02-24 |issn=0261-3077}}</ref> over the "Error 53" message that some iPhone users experienced after updating their devices. The lawsuit alleged that Apple's software update caused some iPhones to become "permanently bricked," and that the company failed to adequately inform users about the risks of updating their devices.
 
=== 9.7-inch iPad Pro bricking issue ===
Updating an iPhone 6 with a replaced Touch ID sensor to a new version of iOS would cause the update to fail and report an "Error 53.",<ref name="iOS 9.2.1 error 53 fix">{{cite web|url=https://www.cultofmac.com/413066/apple-apologizes-for-error-53-releases-fix/|title=Apple apologizes for Error 53, releases fix {{!}} Cult of Mac|date=February 18, 2016|work=Cult of Mac|access-date=October 28, 2017}}</ref> as a result of additional hardware security checks left unintentionally.<ref name="iOS 9.2.1 error 53 fix"/> This was fixed with a re-release of iOS 9.2.1, with build number 13D20.
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 saw an "Error 56" message that instructs them to plug their devices into iTunes.<ref>{{Cite web |title=iOS 9.3.2 Bricking Some 9.7-inch iPad Pro Devices With 'Error 56' Message [Updated] |url=https://www.macrumors.com/2016/05/16/ios-9-3-2-bricking-some-9-7-ipad-pros/ |access-date=2022-03-22 |website=MacRumors |date=May 16, 2016 |language=en |archive-date=March 22, 2022 |archive-url=https://web.archive.org/web/20220322014132/https://www.macrumors.com/2016/05/16/ios-9-3-2-bricking-some-9-7-ipad-pros/ |url-status=live }}</ref>
 
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>
;Bluetooth
Many iPhone SE owners experienced various issues relating to phone calls via Bluetooth connectivity.<ref>{{cite web|url=https://discussions.apple.com/thread/7521352?start=0&tstart=0 |title=iPhone SE Bluetooth issues|website=Apple Support Communities|accessdate=April 25, 2016}}</ref> This issue was fixed with iOS 9.3.2.
 
=== iPhone 4S lawsuit ===
;Security
{{See also|Batterygate}}
A WebKit rendering component exploit was discovered that threatened users' security by allowing access to device sensors was discovered with the release of 9.3.3. The exploit worked by tricking the user to click on a URL contained in an SMS.<ref>{{cite web|url=https://www.macworld.com/article/3112318/ios/apple-advises-immediate-update-to-ios-9-3-5-after-discovery-of-targeted-iphone-spyware.html |title=Apple advises immediate update to iOS 9.3.5 after discovery of targeted iPhone spyware|work=Macworld|access-date=May 1, 2017}}</ref> This was quickly fixed with the release of 9.3.5.
Apple faced a lawsuit alleging its iOS 9 mobile operating software significantly slowed down the iPhone 4S. The lawsuit sought $5 million from Apple.<ref>{{Cite web |last=Guynn |first=Jessica |title=Apple sued for slowing iPhone 4S with iOS 9 upgrade |url=https://www.usatoday.com/story/tech/news/2015/12/31/apple-lawsuit-iphone-4s-ios-9-mobile-operating-system-upgrade/78134096/ |access-date=2022-03-22 |website=USA TODAY |language=en-US |archive-date=March 22, 2022 |archive-url=https://web.archive.org/web/20220322064305/https://www.usatoday.com/story/tech/news/2015/12/31/apple-lawsuit-iphone-4s-ios-9-mobile-operating-system-upgrade/78134096/ |url-status=live }}</ref><ref>{{Cite web |date=2015-12-30 |title=Class Action Lawsuit Accuses Apple of Slowing Down iPhone 4s With iOS 9 Update {{!}} iPhone in Canada Blog |url=https://www.iphoneincanada.ca/news/class-action-lawsuit-accuses-apple-of-slowing-down-iphone-4s-with-ios-9-update/ |access-date=2022-03-22 |language=en-US |archive-date=June 28, 2022 |archive-url=https://web.archive.org/web/20220628153824/https://www.iphoneincanada.ca/news/class-action-lawsuit-accuses-apple-of-slowing-down-iphone-4s-with-ios-9-update/ |url-status=live }}</ref><ref>{{Cite web |date=2016-01-03 |title=Apple Facing Lawsuit For Allegedly Forcing People To Buy Newer Models By Slowing Down iPhone 4s with iOS 9 |url=https://www.techtimes.com/articles/120915/20160103/apple-facing-lawsuit-for-allegedly-forcing-people-to-buy-newer-models-by-slowing-down-iphone-4s-with-ios-9.htm |url-status=live |access-date=2022-03-22 |archive-date=November 8, 2020 |archive-url=https://web.archive.org/web/20201108114627/http://www.techtimes.com/articles/120915/20160103/apple-facing-lawsuit-for-allegedly-forcing-people-to-buy-newer-models-by-slowing-down-iphone-4s-with-ios-9.htm }}</ref><ref>{{Cite web |title=Class Action Lawsuit Accuses Apple of Crippling iPhone 4s With iOS 9 Update |url=https://www.macrumors.com/2015/12/29/ios9-iphone-4s-lawsuit/ |access-date=2022-03-22 |website=MacRumors |date=December 29, 2015 |language=en |archive-date=March 22, 2022 |archive-url=https://web.archive.org/web/20220322064305/https://www.macrumors.com/2015/12/29/ios9-iphone-4s-lawsuit/ |url-status=live }}</ref>
 
=== iOS 10Bluetooth ===
Many iPhone SE owners experienced various issues relating to phone calls via Bluetooth connectivity.<ref>{{cite web|url=https://discussions.apple.com/thread/7521352?start=0&tstart=0|title=iPhone SE Bluetooth issues|website=Apple Support Communities|access-date=April 25, 2016|archive-date=June 4, 2016|archive-url=https://web.archive.org/web/20160604095344/https://discussions.apple.com/thread/7521352?start=0&tstart=0|url-status=live}}</ref> This issue was fixed with iOS 9.3.2.
 
=== Security ===
A WebKit rendering component exploit was discovered that threatened users' security by allowing access to device sensors was discovered with the release of 9.3.3. The exploit worked by tricking the user to click on a URL contained in an SMS.<ref>{{cite web|url=https://www.macworld.com/article/3112318/ios/apple-advises-immediate-update-to-ios-9-3-5-after-discovery-of-targeted-iphone-spyware.html|title=Apple advises immediate update to iOS 9.3.5 after discovery of targeted iPhone spyware|work=Macworld|access-date=May 1, 2017|archive-date=April 28, 2017|archive-url=https://web.archive.org/web/20170428232206/http://www.macworld.com/article/3112318/ios/apple-advises-immediate-update-to-ios-9-3-5-after-discovery-of-targeted-iphone-spyware.html|url-status=live}}</ref> This was quickly fixed with the release of 9.3.5.
 
== iOS 10 ==
{{main|iOS 10#Problems}}
;"30% battery bug"
 
=== Recovery mode issues ===
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}}</ref> This issue was fixed with the release of iOS 10.3.
The initial iOS 10 update released on September 13, 2016, caused many iPhones and iPads to get stuck in recovery mode, requiring the devices to be connected to a Mac or PC with [[iTunes]] in order to retry the update or restore them to factory settings.<ref>{{Cite web |date=2016-09-14 |title=iPhones 'bricked' as Apple releases iOS 10 (and then rapidly fixes the problem) |url=https://grahamcluley.com/apple-releases-ios-10/ |access-date=2022-03-23 |website=Graham Cluley |language=en-GB |archive-date=January 25, 2022 |archive-url=https://web.archive.org/web/20220125085516/https://grahamcluley.com/apple-releases-ios-10/ |url-status=live }}</ref>
 
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>
As of the iOS 10.2.1 release, iOS throttles CPU performance on iPhones with batteries in poor health. This eventually led to [[Batterygate]] shortly after the iOS 11 release. As a result, Apple announced battery replacements would be $29 instead of $79.<ref>{{cite web|url=https://www.cnbc.com/2017/12/28/apple-batterygate-letter-full-text.html |title=Apple apologizes for iPhone slowdowns and offers $29 battery replacements|date=December 28, 2017|work=Anita Balakrishnan|access-date=January 24, 2018}}</ref> They also announced that iOS 11.3 would show battery health in the Settings > Battery menu and let the user decide if they wanted the previous 30% shutdown behavior or the throttled CPU.<ref>{{cite web|url=https://9to5mac.com/2018/01/24/ios-11-3-beta-1/ |title=Apple releases first iOS 11.3 Developer beta for iPhone and iPad|date=January 24, 2018|work=Zac Hall|access-date=January 24, 2018}}</ref>
 
=== iOS"30% 11battery 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 throttled CPU performance on iPhones with batteries in poor health. Due to poor communication from Apple on the addition of this feature, suspicions about [[planned obsolescence]] arose, which eventually led to the [[Batterygate]] controversy shortly after the release of iOS 11. As a result, Apple announced battery replacements would be $29 instead of $79.<ref>{{cite web|url=https://www.cnbc.com/2017/12/28/apple-batterygate-letter-full-text.html|title=Apple apologizes for iPhone slowdowns and offers $29 battery replacements|date=December 28, 2017|work=Anita Balakrishnan|access-date=January 24, 2018|archive-date=January 13, 2018|archive-url=https://web.archive.org/web/20180113153646/https://www.cnbc.com/2017/12/28/apple-batterygate-letter-full-text.html|url-status=live}}</ref> They also announced that iOS 11.3 would show battery health in the Settings > Battery menu and let the user decide if they wanted the previous 30% shutdown behavior or the throttled CPU.<ref>{{cite web|url=https://9to5mac.com/2018/01/24/ios-11-3-beta-1/|title=Apple releases first iOS 11.3 Developer beta for iPhone and iPad|date=January 24, 2018|work=Zac Hall|access-date=January 24, 2018|archive-date=January 24, 2018|archive-url=https://web.archive.org/web/20180124215214/https://9to5mac.com/2018/01/24/ios-11-3-beta-1/|url-status=live}}</ref>
{{main|iOS 11#Problems}}
;Battery
Many users reported worse battery life with iOS 11 than with iOS 10.3.3.<ref>{{Citation |title=DO NOT install iOS 11 before Watching this Video|date=September 13, 2017|url=https://www.youtube.com/watch?v=WOHkKnRz4cI|accessdate=October 28, 2017}}</ref> This issue was addressed with the release of iOS 11.1.<ref>{{cite web|url=http://bgr.com/2017/10/24/ios-11-1-battery-drain-fix-iphone-8/ |title=iOS 11 will dramatically improve battery life on all iPhones|date=October 24, 2017|work=BGR|access-date=October 31, 2017}}</ref>
 
=== Crash caused by 5-second video ===
;Calculator
On November 22, 2016, a five-second video file originally named "IMG_0942.MP4" started crashing iOS on an increasing count of devices, forcing users to reboot. It [[Viral video|gained massive popularity]] through social media channels and messaging services.<ref>{{cite web |last1=Warren |first1=Tom |date=2016-11-22 |title=This 5-second video will crash your iPhone |url=https://www.theverge.com/2016/11/22/13713178/iphone-crash-video-mp4-bug |url-status=live |archive-url=https://web.archive.org/web/20210624195120/https://www.theverge.com/2016/11/22/13713178/iphone-crash-video-mp4-bug |archive-date=June 24, 2021 |access-date=June 13, 2021 |website=The Verge |language=en}}</ref>
 
== iOS 11 ==
Due to an animation bug, quickly typing in an equation caused the built-in Calculator app to display incorrect answers.<ref>{{cite web|url=https://www.macrumors.com/2017/10/24/ios-11-calculator-animation-bug/ |title=iOS 11 Bug: Typing 1+2+3 Quickly in the Calculator App Won't Get You 6|access-date=December 2, 2017}}</ref> The bug was fixed in iOS 11.2.
{{main|iOS 11#Problems}}
 
=== Calculator ===
;Mail
Due to a bug related to UI animation, quickly typing in an equation caused the built-in Calculator app to give incorrect answers.<ref>{{cite web|url=https://www.macrumors.com/2017/10/24/ios-11-calculator-animation-bug/|title=iOS 11 Bug: Typing 1+2+3 Quickly in the Calculator App Won't Get You 6|date=October 24, 2017 |access-date=December 2, 2017|archive-date=October 26, 2017|archive-url=https://web.archive.org/web/20171026165113/https://www.macrumors.com/2017/10/24/ios-11-calculator-animation-bug/|url-status=live}}</ref> The bug was fixed in iOS 11.2.
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}}</ref> This has been resolved with the release of iOS 11.0.1.<ref name="ios_11_0_1_exchange_fix">{{cite web|url=https://arstechnica.com/gadgets/2017/09/apples-ios-11-0-1-update-addresses-exchange-e-mail-server-issue |title=Apple's iOS 11.0.1 update addresses Exchange email server issue|author=Samuel Axon|date=September 26, 2017|website=[[Ars Technica]]}}</ref>
 
=== Mail ===
;AutoCorrect
Users complainedwith ofOutlook.com, aOffice bug365, inand thecertain built-in[[Microsoft keyboardExchange inServer|Exchange]] iOSaccounts 11were that changed the letter "I"unable to "Asend [?]"email.<ref>{{cite web|url=https://wwwsupport.telegraphapple.co.ukcom/technology/2017/11/06/iphonesen-autocorrecting-letter-incomprehensible-symbolus/ HT208136|title=iPhonesIf areyou autocorrectingcan't thesend letteran 'i'email towith iOS 11 and an incomprehensibleOutlook.com symbol|date=Novemberor 6,Exchange 2017mail account|work=TheApple TelegraphSupport|access-date=NovemberSeptember 2225, 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 was fixedresolved with the release of iOS 11.10.1.<ref name="ios_11_0_1_exchange_fix">{{cite web|url=https://arstechnica.com/gadgets/2017/1109/apples-ios-11-10-1-isupdate-hereaddresses-itexchange-fixese-themail-autocorrect-bug-and-a-hey-siriserver-issue/ |title=Apple's iOS 11.10.1 isupdate here:addresses ItExchange fixesemail theserver autocorrectissue|author=Samuel bugAxon|date=September and a26, "Hey Siri" issue2017|workwebsite=[[Ars Technica]]|access-date=NovemberJuly 2215, 2020|archive-date=July 27, 2020|archive-url=https://web.archive.org/web/20200727201659/https://arstechnica.com/gadgets/2017/09/apples-ios-11-0-1-update-addresses-exchange-e-mail-server-issue/|url-status=live}}</ref>
 
=== AutoCorrect ===
;December 2 respring
Users complained of a bug in the built-in keyboard in iOS 11 that changed the letter "I" to "A [?]", if automatic correction was enabled.<ref>{{cite web|url=https://www.telegraph.co.uk/technology/2017/11/06/iphones-autocorrecting-letter-incomprehensible-symbol/|title=iPhones are autocorrecting the letter 'i' to an incomprehensible symbol|date=November 6, 2017|work=The Telegraph|access-date=November 22, 2017|archive-date=November 9, 2017|archive-url=https://web.archive.org/web/20171109104204/http://www.telegraph.co.uk/technology/2017/11/06/iphones-autocorrecting-letter-incomprehensible-symbol/|url-status=live}}</ref> This was fixed with the release of iOS 11.1.1.<ref>{{cite web|url=https://arstechnica.com/gadgets/2017/11/ios-11-1-1-is-here-it-fixes-the-autocorrect-bug-and-a-hey-siri-issue/|title=iOS 11.1.1 is here: It fixes the autocorrect bug and a "Hey Siri" issue|work=Ars Technica|date=November 9, 2017 |access-date=November 22, 2017|archive-date=December 1, 2017|archive-url=https://web.archive.org/web/20171201041238/https://arstechnica.com/gadgets/2017/11/ios-11-1-1-is-here-it-fixes-the-autocorrect-bug-and-a-hey-siri-issue/|url-status=live}}</ref>
 
=== December 2 respring ===
A bug in iOS 11 was present that would cause the device to constantly respring and crash if an app sends local notifications on or after 00:15 on December 2, 2017. Apple responded by releasing iOS 11.2 early, which fixed the bug.<ref>{{cite web|url=https://www.macrumors.com/2017/12/02/ios-11-1-2-date-bug-crash-loop/ |title=Date Bug in iOS 11.1.2 Causing Crash Loop on iPhones as December 2 Hits [Updated]|access-date=December 2, 2017}}</ref>
A bug in iOS 11 was present that would cause the device's home screen to constantly crash if an app sent local notifications on or after 00:15 on December 2, 2017. Apple responded by releasing iOS 11.2 early, which fixed the bug.<ref>{{cite web|url=https://www.macrumors.com/2017/12/02/ios-11-1-2-date-bug-crash-loop/|title=Date Bug in iOS 11.1.2 Causing Crash Loop on iPhones as December 2 Hits [Updated]|date=December 2017 |access-date=December 2, 2017|archive-date=December 4, 2017|archive-url=https://web.archive.org/web/20171204081111/https://www.macrumors.com/2017/12/02/ios-11-1-2-date-bug-crash-loop/|url-status=live}}</ref>
 
;=== Telugu character crash ===
A bug was present in iOS 10 and 11 that would cause an app to crash when a certain Telugusequence character(జ్ఞof Telugu ‌ా)characters was pasted into it, or for the phone's tohome respringscreen if pasted into Spotlight.<ref>{{Citation |title=This Indian Text Will Crash ANY iPhone!జ్ఞ ‌ా|date=February 15, 2018|url=https://wwwsearch.youtube.com/watch?v=K73fw99Xb9s|accessdate=February 19, 2018}}</ref> The bug was fixed with iOS 11.2.6.<ref>{{cite web|url=https://9to5mac.com/2018/02/19/telugu-character-fix/ |title=Apple releases iOS 11.2.6, watchOS 4.2.3, tvOS 11.2.6, and macOS 10.13.3 supplemental update including Telugu character fix|date=February 19, 2018|work=9to5Mac|access-date=February 19, 2018|archive-date=February 20, 2018|archive-url=https://web.archive.org/web/20180220031558/https://9to5mac.com/2018/02/19/telugu-character-fix/|url-status=live}}</ref>
 
;=== iPhone 8 touchscreen issues after third -party repair ===
A bug withThe iOS 11.3 update caused some iPhone 8 devices that had had their screens repaired by a third party repair shop to become unusable by disabling the touch screen. Apple corrected this issue by releasing iOS 11.3.1.<ref>{{cite web |url=https://www.macrumors.com/2018/04/24/apple-releases-ios-11-3-1-update/ |title=Apple Releases iOS 11.3.1 Update With Fix for Third-Party Display Repair Issue |websitedate=April 24, 2018 |access-date=July 15, 2020 |archive-date=September 23, 2020 |archive-url=https://web.archive.org/web/20200923172125/https://www.macrumors.com/2018/04/24/apple-releases-ios-11-3-1-update/ |url-status=live }}</ref>
 
=== iOS 12 ===
{{main|iOS 12#Problems}}
;Group FaceTime Bug
{{main|FaceTime#Group FaceTime Bug}}
A privacy issue was discovered when using [[FaceTime]] in iOS 12.1. This bug allowed users to [[eavesdrop]] the recipient with access to their camera and audio without them answering the call and their knowledge when adding another person to the call. As a result, Apple had permanently disabled Group FaceTime in iOS versions 12.1 to 12.1.3. An update was later released on 12.1.4 to fix the bug.<ref>{{Cite web|url=https://www.minicreo.com/ios-12-problems/|title='FaceTime Eavesdropping Issue' in iOS 12 |last=Woods |first= Kelly |date=24 May 2019|accessdate=24 May 2019}}</ref>
 
=== Group FaceTime bug ===
;Sending iMessages to the wrong contacts
{{main|FaceTime#Group FaceTime bug}}
iOS 12 merges conversation history for devices using a shared Apple ID, even if separate handles are used, such as unique phone numbers or email Fixes. As a result, iMessages may be delivered to the wrong device.<ref>{{cite web|url=https://mashable.com/article/apple-ios-12-merged-messages-wrong-contacts |title=Apple users claim iOS 12 is sending iMessages to the wrong contacts |website=Mashable |accessdate=October 25, 2018}}</ref>
A privacy issue was discovered when using [[FaceTime]] in iOS 12.1 that allowed users to [[eavesdrop]] the recipient with access to their camera and audio without them answering the call and their knowledge when adding another person to the call. As a result, Apple disabled Group FaceTime entirely in iOS versions 12.1 to 12.1.3. An update was later released on 12.1.4 to fix the bug.<ref>{{Cite web|url=https://www.minicreo.com/ios-12-problems/|title='FaceTime Eavesdropping Issue' in iOS 12|last=Woods|first=Kelly|date=24 May 2019|access-date=24 May 2019|archive-date=April 11, 2022|archive-url=https://web.archive.org/web/20220411054349/https://www.minicreo.com/ios-12-problems/|url-status=live}}</ref>
 
=== Sending iMessages to the wrong contacts ===
iOS 12 merged conversation history for devices using a shared Apple ID even if separate handles were used, such as unique phone numbers or email addresses. As a result, iMessages may have been delivered to the wrong device.<ref>{{cite web |url=https://mashable.com/article/apple-ios-12-merged-messages-wrong-contacts |title=Apple users claim iOS 12 is sending iMessages to the wrong contacts |website=Mashable |date=October 2018 |access-date=October 25, 2018 |archive-date=October 25, 2018 |archive-url=https://web.archive.org/web/20181025180555/https://mashable.com/article/apple-ios-12-merged-messages-wrong-contacts/ |url-status=live }}</ref>
 
=== iOS 12.3.2 update incompatibility ===
The iOS 12.3.2 update, released for iPhone 8 Plus devices only, caused users to be unable to transfer backups for this version to a different iPhone model as only the iPhone 8 Plus has this software update.<ref>{{Cite web|last=Lee|first=Cody|date=2019-06-27|title=Issues restoring from iOS 12.3.2? Here are some workarounds|url=https://www.idownloadblog.com/2019/06/27/fixing-the-ios-12-3-2-restore-issue/|access-date=2021-01-30|website=iDownloadBlog.com|language=en-US|archive-date=December 4, 2020|archive-url=https://web.archive.org/web/20201204234546/https://www.idownloadblog.com/2019/06/27/fixing-the-ios-12-3-2-restore-issue/|url-status=live}}</ref>
 
=== iOS 12.4 jailbreak ===
A kernel vulnerability that was fixed in iOS 12.3 was accidentally restored in iOS 12.4. This made iOS 12.4 vulnerable to exploits using the vulnerability, and a jailbreak was released.<ref>{{Cite web|last=Miller|first=Chance|date=2019-08-19|title=iOS 12.4 jailbreak publicly released for modern iPhones|url=https://9to5mac.com/2019/08/19/ios-12-4-jailbreak-released/|access-date=2021-01-30|website=9to5Mac|language=en-US|archive-date=November 7, 2020|archive-url=https://web.archive.org/web/20201107224738/https://9to5mac.com/2019/08/19/ios-12-4-jailbreak-released/|url-status=live}}</ref> Later, the kernel vulnerability was patched again by Apple in iOS 12.4.1.<ref>{{Cite web|last=Miller|first=Chance|date=2019-08-26|title=Apple releases iOS 12.4.1 with jailbreak vulnerability fix|url=https://9to5mac.com/2019/08/26/ios-12-4-1-jailbreak-release-fix/|access-date=2021-01-30|website=9to5Mac|language=en-US|archive-date=January 22, 2021|archive-url=https://web.archive.org/web/20210122132143/https://9to5mac.com/2019/08/26/ios-12-4-1-jailbreak-release-fix/|url-status=live}}</ref>
 
== 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 ===
After the release of iOS 13.2, reports followed about applications being cleared from memory at a higher rate than in iOS 13.1, including on the then latest iPhone models.<ref>{{Cite web|last=Statt|first=Nick|date=2019-10-31|title=iOS 13 is killing background apps more frequently, iPhone owners report|url=https://www.theverge.com/2019/10/31/20942043/apple-ios-13-iphone-11-pro-ram-memory-management-app-background-refresh|access-date=2021-01-30|website=The Verge|language=en|archive-date=February 5, 2021|archive-url=https://web.archive.org/web/20210205082056/https://www.theverge.com/2019/10/31/20942043/apple-ios-13-iphone-11-pro-ram-memory-management-app-background-refresh|url-status=live}}</ref> Apple attempted to fix the issue twice in iOS 13.2.2<ref>{{Cite web|last=Miller|first=Chance|date=2019-11-07|title=iOS 13.2.2 now available with fix for background app performance, more|url=https://9to5mac.com/2019/11/07/ios-13-2-2-now-available-with-fix-for-background-app-performance-more/|access-date=2021-01-30|website=9to5Mac|language=en-US|archive-date=November 7, 2019|archive-url=https://web.archive.org/web/20191107182224/https://9to5mac.com/2019/11/07/ios-13-2-2-now-available-with-fix-for-background-app-performance-more/|url-status=live}}</ref> and iOS 13.3.<ref>{{Cite web|last=Miller|first=Chance|date=2019-11-05|title=What's new in iOS 13.3 developer beta 1?|url=https://9to5mac.com/2019/11/05/whats-new-in-ios-13-3-developer-beta-1/|access-date=2021-01-30|website=9to5Mac|language=en-US|quote=Early tests indicate that iOS 13.3 does solve this problem, at least to a certain degree. [...] Apparent fix for iOS 13.2 RAM management problems, though there are mixed reports|archive-date=November 12, 2020|archive-url=https://web.archive.org/web/20201112013353/https://9to5mac.com/2019/11/05/whats-new-in-ios-13-3-developer-beta-1/|url-status=live}}</ref>
 
=== 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 saw problems experienced a "white swirl" on both of their HomePods, or an endless reset loop. As a result, the update for the HomePod was withdrawn by Apple.<ref>{{Cite web |last=Espósito |first=Filipe |date=2019-10-28 |title=Some users experiencing bricked HomePod after updating to iOS 13.2 [Update: pulled] |url=https://9to5mac.com/2019/10/28/some-users-experiencing-bricked-homepod-after-updating-to-ios-13-2/ |access-date=2022-03-21 |website=9to5Mac |language=en-US |archive-date=May 18, 2022 |archive-url=https://web.archive.org/web/20220518222510/https://9to5mac.com/2019/10/28/some-users-experiencing-bricked-homepod-after-updating-to-ios-13-2/ |url-status=live }}</ref><ref>{{Cite web |title=New 13.2 Update Bricking Some HomePods [Update Pulled by Apple] |url=https://www.macrumors.com/2019/10/28/new-13-2-update-bricking-some-homepods/ |access-date=2022-03-21 |website=MacRumors |date=October 28, 2019 |language=en |archive-date=March 14, 2022 |archive-url=https://web.archive.org/web/20220314070611/https://www.macrumors.com/2019/10/28/new-13-2-update-bricking-some-homepods/ |url-status=live }}</ref> Apple advised some users not to install iOS 13.2 on the HomePod and to not reset the HomePod after installing iOS 13.2.{{Citation needed|date=January 2024|reason="Apple advised some users not to install iOS 13.2 on the HomePod and to not reset the HomePod after installing iOS 13.2."}} This issue was fixed with the release of iOS 13.2.1.{{Citation needed|date=January 2024|reason="This issue was fixed with the release of iOS 13.2.1."}}
 
=== iOS 13.5 jailbreak ===
A jailbreak software called Unc0ver was updated in May 2020 with an exploit targeting devices running iOS 11 and above, including the then-latest iOS 13.5. The issue was fixed with iOS 13.5.1.<ref>{{Cite web|last=Gartenberg|first=Chaim|date=2020-06-01|title=Apple releases iOS 13.5.1, patching out the Unc0ver jailbreak|url=https://www.theverge.com/2020/6/1/21277281/apple-ios-13-5-1-patch-unc0ver-jailbreak-update-software-install|access-date=2021-01-30|website=The Verge|language=en|archive-date=December 17, 2020|archive-url=https://web.archive.org/web/20201217073212/https://www.theverge.com/2020/6/1/21277281/apple-ios-13-5-1-patch-unc0ver-jailbreak-update-software-install|url-status=live}}</ref>
 
== iOS 14 ==
 
=== Missing keyboard for Spotlight search ===
The keyboard did not appear when using the Spotlight search function.<ref>{{Cite web|last=September 2020|first=Henry T. Casey 19|title=iOS 14 bugs are messing with apps — what to do now|url=https://www.tomsguide.com/news/ios-14-bugs-are-messing-with-apps-what-to-do-now|access-date=2021-01-30|website=Tom's Guide|date=September 19, 2020 |language=en|archive-date=September 19, 2020|archive-url=https://web.archive.org/web/20200919233424/https://www.tomsguide.com/news/ios-14-bugs-are-messing-with-apps-what-to-do-now|url-status=live}}</ref>
 
=== Default app setting reset ===
The ability to change the default app for messages, email, web browsing, or other services was reset to the stock app every time the device was reset or turned off.<ref>{{Cite web|last=Welch|first=Chris|date=2020-09-17|title=iOS 14 switches default apps back to Apple's Safari and Mail after a reboot|url=https://www.theverge.com/2020/9/17/21444035/ios-14-default-apps-setting-switches-back-safari-mail-bug|access-date=2021-01-30|website=The Verge|language=en|archive-date=February 9, 2021|archive-url=https://web.archive.org/web/20210209165509/https://www.theverge.com/2020/9/17/21444035/ios-14-default-apps-setting-switches-back-safari-mail-bug|url-status=live}}</ref> Apple attempted to fix the issue with iOS 14.0.1.<ref>{{Cite web|last=Krasnoff|first=Barbara|date=2020-09-24|title=Apple update fixes iOS 14 issue with default mail and browser apps|url=https://www.theverge.com/2020/9/24/21454861/apple-ios14-iphone-ipad-fix-default-mail-browser|access-date=2021-01-30|website=The Verge|language=en|archive-date=January 18, 2021|archive-url=https://web.archive.org/web/20210118171811/https://www.theverge.com/2020/9/24/21454861/apple-ios14-iphone-ipad-fix-default-mail-browser|url-status=live}}</ref>
 
=== 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 caused [[Image Capture]] to fail to import photos on computers running macOS Mojave and older. This was fixed in the iOS 16.1 update.<ref>{{Cite web |last=Leon |first=Jean |date=2022-10-25 |title=iOS 16 users unable to import photos via iTunes on macOS Mojave |url=https://piunikaweb.com/2022/10/25/ios-16-users-unable-to-import-photos-via-itunes-on-macos-mojave/ |access-date=2023-12-08 |website=PiunikaWeb |language=en-US}}</ref>
 
=== Activation issues ===
There was a bug which caused activation issues on the iPhone 14. This was fixed in iOS 16.0.1.<ref>{{Cite web|title=Apple warns of iPhone 14 activation issues on launch day |url=https://www.macworld.com/article/1069541/iphone-14-ios-16-0-1-activation-issues.html |access-date=2023-12-08 |website=Macworld |language=en}}</ref>
 
=== Camera shaking issues ===
There was a bug which caused shaking in the Camera app for iPhone 14 Pro/Pro Max users. This was fixed in iOS 16.0.2.<ref>{{Cite web |title=UPDATE: Fix on the way for iPhone 14 Pro 'camera shake' bug |url=https://www.macworld.com/article/1070221/iphone-14-pro-camera-shake-bug-tiktok-instagram-snapchat.html |access-date=2023-12-08 |website=Macworld |language=en}}</ref>
 
=== Copy and paste alerts ===
Some iOS 16 users complained about excessive alerts when copying and pasting content from multiple apps. Apple attempted to fix this issue in iOS 16.0.2, but according to some reports, it was only fixed in iOS 16.1.<ref>{{Cite web |last=Cross |first=Jason |title=iOS 16.0.2 brings important fixes to new, old iPhones |url=https://www.macworld.com/article/1073336/ios-16-0-2-iphone-14-camera-shake-copy-paste.html |access-date=2023-12-08 |website=Macworld |language=en}}</ref><ref>{{Cite web |last=Miller |first=Chance |date=September 20, 2022 |title=iOS 16.1 beta 2 no longer wants your permission to paste every single time |url=https://9to5mac.com/2022/09/20/ios-16-copy-paste-alert/ |access-date=December 8, 2023 |website=9to5Mac}}</ref>
 
=== 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 appeared to affect iCloud Mail. Apple fixed the issue in iOS 16.0.3.<ref>{{Cite web |date=2022-09-22 |title=iOS 16 Mail can be crashed by a specific 'from' field |url=https://appleinsider.com/articles/22/09/22/ios-16-mail-can-be-crashed-by-a-specific-from-field |access-date=2023-12-08 |website=AppleInsider |language=en}}</ref>
 
=== Camera app slowdowns ===
There were reports that the Camera app was slow to open on the iPhone 14 series phones. Apple fixed this issue in iOS 16.0.3.<ref name=":0">{{Cite web |title=Apple releases iOS 16.0.3 with iPhone 14, Mailjack fixes ahead of iOS 16.1 |url=https://www.macworld.com/article/1348444/ios-16-0-3-iphone-14-camera-carplay-mailjack.html |access-date=2023-12-08 |website=Macworld |language=en}}</ref>
 
=== Missing notifications ===
Some users reported that incoming notifications (including calls) were not being displayed. This was fixed in iOS 16.0.3.<ref name=":0" />
 
=== CarPlay microphone issues ===
Prior to iOS 16.0.3, some CarPlay users reported low microphone volume when they spoke during phone calls with their iPhone connected to CarPlay. Apple fixed this issue in iOS 16.0.3.<ref name=":0" />
 
=== WiFi issues ===
Some users reported that their WiFi connection was being lost after updating to iOS 16.1. Apple fixed this issue in iOS 16.1.1.<ref>{{Cite web |title=Apple releases iOS 16.1.1 with bug fixes and critical security updates |url=https://www.macworld.com/article/1375998/ios-ipad-16-1-1-bug-fixes-security-updates.html |access-date=2023-12-08 |website=Macworld |language=en}}</ref><ref>{{Cite web |date=2022-11-07 |title=Apple Preparing iOS 16.1.1 as Widespread Wi-Fi Bug Persists |url=https://www.macrumors.com/2022/11/07/apple-working-on-ios16-1-1/ |access-date=2023-12-08 |website=MacRumors |language=en}}</ref>
 
=== iPhone 14 Pro series "horizontal lines" issue ===
In December 2022, reports surfaced of an issue in the iPhone 14 Pro series that caused horizontal lines to appear when said phones started up. Apple fixed this issue in iOS 16.3.<ref>{{Cite web |date=2022-12-23 |title=iPhone 14 Pro Series Users Complain About Horizontal Lines on Display: Report |url=https://www.gadgets360.com/mobiles/news/iphone-14-pro-max-horizontal-lines-flashing-display-reddit-users-apple-community-forum-3632686 |access-date=2023-12-08 |website=Gadgets 360 |language=en}}</ref><ref>{{Cite web |last=Kelly |first=Gordon |title=Apple Confirms Display Problem For iPhone 14 Pro, iPhone 14 Pro Max Buyers |url=https://www.forbes.com/sites/gordonkelly/2023/01/17/apple-iphone-14-pro-max-screen-problem-horizontal-lines-ios-update-fix/ |access-date=2023-12-08 |website=Forbes |language=en}}</ref><ref name=":1">{{Cite web |last=Haslam |first=Karen |title=iOS 16 superguide: Everything you need to know about the latest version |url=https://www.macworld.com/article/631448/ios-16-features-compatibility-how-to-update.html |access-date=2023-12-08 |website=Macworld |language=en}}</ref>
 
=== Messages and Photos vulnerabilities ===
There were a large number of security issues (including [[Superuser|root]] access issues) with Messages and Photos that Apple patched in iOS 16.3.<ref>{{Cite web |last=Simon |first=Michael |title='Large new class of bugs' leaves Messages and Photos vulnerable in iOS and macOS |url=https://www.macworld.com/article/1519040/ios-16-3-macos-13-2-security-update-crash-reporter-foundation-code-root.html |access-date=2023-12-08 |website=Macworld |language=en}}</ref>
=== Storage issues ===
Some users reported that storage took over their space on iOS 16.4. When they tried to clear storage, the storage would not free up. Apple fixed this issue in iOS 16.5.{{cn|date=March 2024}}
 
=== Weather app issues ===
Some users experienced Weather app issues on iOS 16.4. Apple reportedly fixed this issue in iOS 16.4.1.<ref>{{Cite web |title=iOS 16.4.1 arrives with critical security updates, bug fixes |url=https://www.macworld.com/article/1780577/ios-16-4-1-bug-fixes-security-updates.html |access-date=2023-12-08 |website=Macworld |language=en}}</ref>
 
=== Screen Time issues ===
Some users reported that their Screen Time settings did not sync across devices. Apple reportedly fixed this issue in iOS 16.5.<ref name=":1" />
 
== iOS 17 ==
 
=== iPhone 15 Pro thermal issues ===
Some users reported that some [[iPhone 15 Pro]] models were prone to overheating. Apple insisted that the overheating issue was related to a [[software bug]] and was not related to the new hardware or design in the [[iPhone 15 Pro]] models, which introduced a new titanium frame with an aluminum substructure to replace the stainless steel frame from the past several Pro models. Since iOS 17.0.3 was released, new reports surfaced of other overheating issues not related to fast-charging. The issue was resolved in iOS 17.1 after Apple fixed a software bug relating to the issue.<ref>{{Cite web |title=iPhone 15 Pro overheating: Thermal photos before and after iOS 17.0.3 |url=https://www.zdnet.com/article/iphone-15-pro-overheating-thermal-photos-before-and-after-ios-17-0-3/ |access-date=2023-10-23 |website=ZDNET |language=en}}</ref><ref>{{Cite web |title=New iPhone 15 Pro overheating reports: Still too hot after iOS 17.0.3 and fresh issues arise after the update |url=https://www.zdnet.com/article/new-iphone-15-pro-overheating-reports-still-too-hot-after-ios-17-0-3-and-fresh-issues-arise-after-the-update/ |access-date=2023-10-23 |website=ZDNET |language=en}}</ref>
 
=== 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 ===
Some users reported that their iPhone 15 series phones were experiencing [[screen burn-in]]. Apple fixed this issue with iOS 17.1, and clarified that the issue was [[image persistence]], as opposed to screen burn-in, which it was being referred to at the time. The difference is that screen burn-in is a hardware issue that requires a screen replacement, but image persistence can be fixed with a software update.<ref>{{Cite web |last=McGregor |first=Janhoi |title='Incredible' iOS 17.1 Update Has Fixed New iPhone 15 Screen Problem |url=https://www.forbes.com/sites/jaymcgregor/2023/10/20/incredible-ios-171-update-has-fixed-new-iphone-15-screen-problem/ |access-date=2023-12-03 |website=Forbes |language=en}}</ref><ref>{{Cite web |title=Your new iPhone 15 suffering from screen burn-in? Apple has some good news for you |url=https://www.zdnet.com/article/your-new-iphone-15-suffering-from-screen-burn-in-apple-has-some-good-news-for-you/ |access-date=2023-12-03 |website=ZDNET |language=en}}</ref><ref>{{Cite web |date=2023-10-19 |title=Facing "screen burn-in" on your iPhone 15 Pro? Apple has a fix for you |url=https://www.androidauthority.com/apple-iphone-15-pro-screen-burn-in-ios171-fix-3377611/ |access-date=2023-12-03 |website=Android Authority |language=en}}</ref>
 
=== Shutdown issues ===
Some users reported that their iPhones turned off temporarily at night, interrupting alarms and other iPhone features. This affected both iPhone 15 models and older devices{{Which|date=January 2024}} as well, suggesting that the bug was related to iOS 17.<ref>{{Cite web |date=2023-10-11 |title=Some iPhone Models Mysteriously Shutting Off at Night |url=https://www.macrumors.com/2023/10/11/iphone-models-turning-off-at-night/ |access-date=2023-10-23 |website=MacRumors |language=en}}</ref>
 
=== App switcher appears while typing ===
;iOS 12.3.2 update incompatibility
A hard-to-replicate bug caused the app switcher to appear during typing for some users. It was possible to work around this issue by disabling the ''Reachability'' feature.<ref>{{Cite web |date=2023-12-05 |title=iOS 17 Bug Switches Apps While Typing - How to Fix |url=https://www.macrumors.com/how-to/ios-17-bug-switches-apps-while-typing-fix/ |access-date=2023-12-08 |website=MacRumors |language=en}}</ref>
The iOS 12.3.2 update, released for iPhone 8 Plus devices only, caused users to be unable to transfer backups for this version to a different iPhone as only the 8 Plus has this software update.
 
=== iOS 17.3 beta 2 boot loop ===
;iOS 12.4 jailbreak
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 was related to the Back Tap feature.<ref>{{Cite web |last=Clover |first=Juli |date=2024-01-03 |title=Apple Pulls iOS 17.3 Beta 2 Due to Boot Loop Issue |url=https://www.macrumors.com/2024/01/03/apple-pulls-ios-17-3-beta-2/ |website=MacRumors |access-date=2024-01-08 |language=en}}</ref><ref>{{Cite web |last=Render |first=Josh |date=2024-01-04 |title=Apple pulls iOS 17.3 beta after just 3 hours due to boot loop chaos |url=https://www.tomsguide.com/news/ios-173-beta-pulled-due-to-booting-issues-heres-what-we-know |website=Tom's Guide |access-date=2024-01-08 |language=en}}</ref>
Apple accidentally undid a fix to a kernel code execution exploit (Sock Puppet) that was fixed in iOS 12.3. This made iOS 12.4 vulnerable to the exploit, and a jailbreak was released. Later, the kernel vulnerability was patched again by Apple in iOS 12.4.1.
 
=== iOSText 13auto-completion issues ===
;iOS 13.5 jailbreak
 
Users of iOS 17 were experiencing text auto-completion inserting duplicate or overlapping words, or words being inserted at the wrong spot. This behavior was fixed with iOS 17.3.1.<ref>{{Cite web |last=Clover |first=Juli |date=2024-02-08 |title=Apple Releases iOS 17.3.1 With Fix for Text Bug |url=https://www.macrumors.com/2024/02/08/apple-releases-ios-17-3-1-with-fix-for-text-bug/ |access-date=2024-03-13 |website=MacRumors |language=en}}</ref><ref>{{Cite web |last=Funk |first=Ben |date=2024-02-09 |title=Apple's Surprise iOS 17.3.1 Update Fixes Your iPhone's AI-Fueled Text Entry Woes |url=https://hothardware.com/news/ios-17-text-entry-bug-fix |access-date=2024-03-13 |website=HotHardware |language=en-us}}</ref><ref>{{Cite web|title=About iOS 17 Updates|url=https://support.apple.com/en-us/109043#:~:text=com/kb/HT201222-,iOS%2017.3.1,-This%20update%20provides|access-date=2024-03-13|website=support.apple.com|language=en|archive-url=https://web.archive.org/web/20240313084254/https://support.apple.com/en-us/109043|archive-date=2024-03-13}}</ref>
A jailbreak software called Unc0ver was updated in May 2020 with an exploit targeting devices running iOS 11 and above, including the then-latest iOS 13.5. Apple quickly fixed this with iOS 13.5.1.
 
=== iOSPhotos 14reappearing ===
After updating to iOS 17.5, some users reportedly experienced a bug which caused some of their deleted photos to reappear on their devices.<ref>{{Cite web |date=2024-05-15 |title=Troubling iOS 17.5 Bug Reportedly Resurfacing Old Deleted Photos |url=https://www.macrumors.com/2024/05/15/ios-17-5-bug-deleted-photos-reappear/ |access-date=2024-05-16 |website=MacRumors |language=en}}</ref><ref>{{cite web |url=https://9to5mac.com/2024/05/17/ios-17-5-deleted-photos-app-bug/ |title=iOS 17.5 is allegedly resurfacing pictures that were deleted years age |first=Chance |last=Miller |date=2024-05-17 |access-date=2024-05-18 |website=9to5Mac}}</ref> iOS 17.5.1 was released to fix this issue, which according to Apple, was 'rare' and caused by database corruption.<ref>{{cite magazine|url=https://www.forbes.com/sites/kateoflahertyuk/2024/05/21/ios-1751-emergency-fix-issued-to-all-iphoneusers/ |title=iOS 17.5.1—Emergency Fix Issued To All iPhone Users |first=Kate |last=O'Flaherty |date=2024-05-21 |access-date=2024-05-22 |magazine=[[Forbes]]}}</ref><ref>{{cite magazine|url=https://www.macworld.com/article/2338872/ios-17-5-1-update-fixes-rare-bug-that-caused-some-deleted-photos-to-return.html |title=Update to iOS 17.5.1 to make sure your embarrassing old photos don’t resurface |first=Jason |last=Cross |date=2024-05-21 |access-date=2024-05-22 |magazine=[[Macworld]]}}</ref>
The initial release saw iPhone 11 Pro/11 Pro Max devices being rendered unusable if the battery was drained to zero; this has been corrected.
 
== iOS 18 ==
The ability to change the default app for messages, email, internet or other services is reset to the default Apple app every time the iPhone, iPod or iPad is reset or turned off.
 
== iOS 26 ==
The iPhone keyboard did not appear for search.<ref>[https://www.tomsguide.com/news/ios-14-bugs-are-messing-with-apps-what-to-do-now iOS 14 bugs are messing with apps]</ref>
 
== See also ==
On 30 September 2020, Apple acknowledged battery drain issue in iOS 14 and released a supporting document that offered the users tricks to fix the poor battery performance and 6 other issues. In this document Apple claimed that unpairing the device with synced Apple Watch followed by erasing all data and settings, and restoring from the backup could be a possible fix for reviving 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|accessdate=2 October 2020|website=The Verge}}</ref>
* [[iPhone OS 3|Issues relating to iPhone OS]]
 
== References ==
Line 173 ⟶ 307:
{{iOS}}
 
[[Category:IOS|*]]