Issues relating to iOS

{{main|iOS 4#Problems}}{{Expand section|date=February 2024}}

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.{{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 }}{{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}} 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, but according to some reports it still exists even in iOS 4.3.1.{{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}}

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.{{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}} 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.{{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}}

{{main|iOS 5#Problems}}

Apple confirmed that several battery life bugs were negatively affecting battery life in iOS 5.{{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}} They attempted to fix these bugs with iOS 5.0.1 and 5.1 but the problem still remained.{{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}} All of these bugs were fixed in iOS 5.1.1.{{citation needed|date=November 2024}}

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{{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}}{{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}}

Some users of the iPhone 4S and iPad (Wi-Fi + Cellular) reported issues with the SIM card in iOS 5.0,{{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}} and even though Apple attempted to fix these issues in version 5.0.1 build 9A406 (for iPhone 4S only), they still remained.{{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}}

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.{{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}} Apple has since released version 5.1.1 in an attempt to fix the problem.

{{main|iOS 6#Problems}}

{{Main article|Apple Maps#Early inaccuracy (2012)}}

Apple admitted that there were several bugs in the mapping app on iOS 6, with cities in the wrong location, some places being missed off altogether, some places misnamed and places of interest in the sea.{{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}}{{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}}{{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}} Problems submitted by users were gradually addressed with daily updates to Maps.{{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 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}}

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.{{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 }}

Location-based reminders did not work for iPads, even though they were promised to work on cellular-enabled devices.{{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 }} 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.{{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 }}

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."{{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}}

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 calendar system versus the Gregorian calendar system.{{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}} Apple did not offer a software update, saying that the bug would resolve on January 7, 2013.{{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}}

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".{{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}} Microsoft suggested several workarounds;{{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}} the bug was fixed with the release of iOS 6.1.2.

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.{{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}}

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.

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,{{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}} and that devices unable to run iOS 7, the fourth-generation iPod Touch and the iPhone 3GS, should upgrade to iOS 6.1.6.

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)

{{main|iOS 7#Problems}}

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 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.{{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}} This was fixed in iOS 7.0.2.{{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}}

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.{{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}}

Creating a CardDAV Account had a bug that required manual fixing of the CardDAV-Server-URL.{{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}}

Users reported seeing significant drain on their devices' battery after installing the update to iOS 7.1.{{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}}

Local domain names could no longer be resolved in Safari,{{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}}{{cite web|url=https://discussions.apple.com/thread/5575236|title=Safari can no longer address .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}} breaking short names on the local network.

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.{{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}} This was fixed in iOS 7.1.

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.{{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}} This issue was addressed by the release of iOS 7.0.6.

iPhone 4S users reported problems with the battery indicator, which would freeze at the same value until the iPhone was restarted.{{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}}{{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}}

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.{{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}} This issue was fixed in iOS 7.1.1.{{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}}

{{main|iOS 8#Problems}}

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.{{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}} 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 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.{{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}} Over-the-air downloads of iOS 8.0.1 were stopped within an hour of the release of the software,{{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}} but many early adopters had been affected. These issues were fixed with the release of iOS 8.0.2 a day later.

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.{{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}} A workaround has been devised by users to repair this issue.{{Unreliable source?|date=January 2024}}{{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}}

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.{{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}}

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.

When a specific sequence of Arabic, Unicode, and English characters are sent through iMessage to a device running iOS 8.0 or later, it causes the device to crash and restart; if the Messages app is then opened, the crash repeats.{{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}} 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.{{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/}}

{{main|iOS 9#Problems}}

Many users reported greatly increased Game Center loading times which in turn caused apps that used Game Center logins to appear to load slowly.{{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}} This was fixed with the release of iOS 9.1.

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.{{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}} 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.",{{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}} as a result of additional hardware security checks left unintentionally. This was fixed with a re-release of iOS 9.2.1, with build number 13D20.

Apple faced a lawsuit filed February 11, 2016{{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}}{{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}}{{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}} 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.

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 are seeing an "Error 56" message that instructs them to plug their devices into iTunes.{{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 }}

As a result, iOS 9.3.2 update was withdrawn.{{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 }} This issue was fixed with a re-release version of iOS 9.3.2 in June 2016, with build number 13F72.{{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 }}

{{See also|Batterygate}}

Apple faced a lawsuit alleging its iOS 9 mobile operating software significantly slowed down the iPhone 4S. The lawsuit filed in New York federal court and first spotted by Apple Insider sought $5 million from Apple.{{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 }}{{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 }}{{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 }}{{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 }}

Many iPhone SE owners experienced various issues relating to phone calls via Bluetooth connectivity.{{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}} This issue was fixed with iOS 9.3.2.

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.{{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}} This was quickly fixed with the release of 9.3.5.

{{main|iOS 10#Problems}}

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.{{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 }}

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.{{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 }}

Many users, especially those owning an iPhone 6s, reported that their phones would shut down automatically with 30% battery left.{{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}} This issue was fixed with the release of iOS 10.3. As of the iOS 10.2.1 release, iOS throttles 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.{{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}} 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.{{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}}

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 gained massive popularity through social media channels and messaging services.{{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}}

{{main|iOS 11#Problems}}

Due to a bug related to UI animation, quickly typing in an equation caused the built-in Calculator app to give incorrect answers.{{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}} The bug was fixed in iOS 11.2.

Users with Outlook.com, Office 365, and certain Exchange accounts were unable to send email.{{cite web|url=https://support.apple.com/en-us/HT208136|title=If you can't send an email with iOS 11 and an Outlook.com or Exchange mail account|work=Apple Support|access-date=September 25, 2017|archive-date=September 26, 2017|archive-url=https://web.archive.org/web/20170926182313/https://support.apple.com/en-us/HT208136|url-status=live}} This has been resolved with the release of iOS 11.0.1.{{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|access-date=July 15, 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}}

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.{{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}} This was fixed with the release of iOS 11.1.1.{{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}}

A bug in iOS 11 was present that would cause the device's home screen to constantly 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.{{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}}

A bug was present in iOS 10 and 11 that would cause an app to crash when a certain sequence of Telugu characters was pasted into it, or for the phone's home screen if pasted into Spotlight search. The bug was fixed with iOS 11.2.6.{{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}}

The 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.{{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 |date=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 }}

{{main|iOS 12#Problems}}

{{main|FaceTime#Group FaceTime bug}}

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 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.{{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}}

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 addresses. As a result, iMessages may be delivered to the wrong device.{{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 }}

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.{{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}}

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.{{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}} Later, the kernel vulnerability was patched again by Apple in iOS 12.4.1.{{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}}

Some users were reporting excessive battery drain following the initial release of iOS 13. IOS 13.1.1 fixed the problem.{{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}}

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.{{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}} Apple attempted to fix the issue twice in iOS 13.2.2{{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}} and iOS 13.3.{{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}}

According to multiple people on the MacRumors forums and Reddit, the 13.2 update "bricked" their HomePods, rendering them unusable. Users who are seeing problems are experiencing 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.{{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 }}{{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 }} 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."}}

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.{{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}}

The keyboard did not appear when using the Spotlight search function.{{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}}

The ability to change the default app for messages, email, web browsing, or other services is reset to the stock app every time the device is reset or turned off.{{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}} Apple attempted to fix the issue with iOS 14.0.1.{{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}}

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.{{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}}

On iOS 16.0, a bug causes Image Capture to fail to import photos on computers running macOS Mojave and older. This was fixed in the iOS 16.1 update.{{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}}

There was a bug which caused activation issues on the iPhone 14. This was fixed in iOS 16.0.1.{{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}}

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.{{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}}

Some iOS 16 users were complaining 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.{{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}}{{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}}

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 appears to affect iCloud Mail. Apple fixed the issue in iOS 16.0.3.{{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}}

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.{{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}}

Some users were reporting that incoming notifications (including calls) were not being displayed. This was fixed in iOS 16.0.3.

Prior to iOS 16.0.3, some CarPlay users were reporting low microphone volume when they spoke during phone calls with their iPhone connected to CarPlay. Apple fixed this issue in iOS 16.0.3.

Some users reporting that their WiFi connection was being lost after updating to iOS 16.1. Apple fixed this issue in iOS 16.1.1.{{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}}{{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}}

In December 2022, reports started to surface of an issue in the iPhone 14 Pro series. This issue caused horizontal lines to appear when said phones start up. Apple fixed this issue in iOS 16.3.{{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}}{{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}}{{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}}

There were a large number of security issues (including root access issues) with Messages and Photos that Apple patched in iOS 16.3.{{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}}

Some users reported that storage took over their space on iOS 16.4. When they tried to clear storage, The storage will not free up. Apple fixed this issue in iOS 16.5.{{cn|date=March 2024}}

Some users were experiencing Weather app issues on iOS 16.4. It is believed that Apple fixed this issue in iOS 16.4.1.{{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}}

Some users were reporting that their Screen Time settings did not sync across devices. Apple has reportedly fixed this issue in iOS 16.5.

Apple has 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 have surfaced of other overheating issues not related to fast-charging. The issue was then resolved in iOS 17.1 after Apple fixed a software bug relating to the issue.{{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}}{{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}}

Prior to the release of iOS 17.1, 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.{{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}}{{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}}{{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}}

Some users reported that their iPhones turned off temporarily at night, interrupting alarms and other iPhone features. This affects both iPhone 15 models and older devices{{Which|date=January 2024}} as well, suggesting that the bug is related to iOS 17.{{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}}

A hard-to-replicate bug causes the app switcher to appear during typing for some users. It is possible to work around this issue by disabling the Reachability feature.{{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}}

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 is related to the Back Tap feature.{{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}}{{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}}

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.{{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}}{{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}}{{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}}{{Non-primary source needed|date=March 2024}}

After updating to iOS 17.5, some users reportedly experienced a bug which caused some of their deleted photos to reappear on their devices.{{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}}{{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}} iOS 17.5.1 was released to fix this issue, which according to Apple, was 'rare' and caused by database corruption.{{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}}{{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}}

{{Reflist|30em}}

{{iOS}}

Category:IOS