Content deleted Content added
→Telugu character crash: avoid including the character sequence Tag: references removed |
No edit summary |
||
| (215 intermediate revisions by 81 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 ==
{{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.<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 5 ==
{{main|iOS 5#Problems}}
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
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
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
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
{{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 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 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
Location-based reminders
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
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
Another bug
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.
[[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
An attacker
{{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 (iOS)|control center]] through the lock screen and tapping on the camera or timer buttons. The
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>
Creating a [[CardDAV]] Account
Local ___domain names
Users
Secure transport failed to validate the authenticity of connection. This issue was addressed by restoring missing validation steps. This
[[iPhone 4S]] users
In iOS 7.1, [[Touch ID]] was not functioning on the [[iPhone 5S]]. The problem
{{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.<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|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-
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/
Many users of older generation devices such as the iPhone 4S and the iPad 2 reported performance issues with iOS 8.
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.{{
When a specific sequence of Arabic, Unicode, and English characters
{{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.<ref>{{cite web|url=https://www.cultofmac.com/390755/beware-this-fix-for-nasty-ios-9-game-center-bug/
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
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.
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 ===
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>
=== iPhone 4S lawsuit ===
{{See also|Batterygate}}
Apple faced a lawsuit alleging its iOS 9 mobile operating software significantly slowed down the iPhone 4S. The lawsuit 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>
=== 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|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}}
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>
=== "30% battery bug" ===
Many users, especially those owning an iPhone 6s, reported that their phones would shut down automatically with 30% battery left.<ref>{{cite web|url=http://clark.com/technology/iphone-battery-drain-apple-bug/|title=Mysterious bug is still shutting down iPhones with 30% battery left|date=January 25, 2017|work=Clark Howard|access-date=October 28, 2017|archive-date=October 29, 2017|archive-url=https://web.archive.org/web/20171029064937/http://clark.com/technology/iphone-battery-drain-apple-bug/|url-status=live}}</ref> This issue was fixed with the release of iOS 10.3. As of the iOS 10.2.1 release, iOS 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>
=== Crash caused by 5-second video ===
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>
{{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.<ref>{{cite web|url=https://www.macrumors.com/2017/10/24/ios-11-calculator-animation-bug/
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
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/
A bug in iOS 11 was present that would cause the device's home screen to constantly crash if an app
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.<ref>{{cite web|url=https://9to5mac.com/2018/02/19/telugu-character-fix/
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.<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 |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 }}</ref>
{{main|iOS 12#Problems}}
{{main|FaceTime#Group FaceTime
A privacy issue was discovered when using [[FaceTime]] in iOS 12.1
=== 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>
===
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>
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>
=== Photos reappearing ===
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>
== iOS 18 ==
== iOS 26 ==
* [[iPhone OS 3|Issues relating to iPhone OS]]
== References ==
Line 202 ⟶ 307:
{{iOS}}
[[Category:IOS
| |||