Issues relating to iOS: Difference between revisions

Revision as of 23:51, 19 December 2020

Revision as of 17:19, 30 January 2021

Line 4:

== Issues by iOS version ==

{{Prose|section|date=January 2021}}

=== iOS 4 ===

{{main|iOS 4#Problems}}

; Alarm clock bugs

The Alarm feature of the built in Clock app in the iPhone and iPod Touch has been plagued by major bugs in all versions of iOS 4. The first bug noticed was the "DST bug" which was first seen when some countries switched to/from daylight saving time from/to standard time in October or November 2010.<ref name="SMH iOS 4 alarm bug">{{cite web|url=https://www.smh.com.au/digital-life/iphone/apple-to-fix-dst-alarm-bug-20101007-168um.html |title=Apple to fix DST alarm bug|date=October 7, 2010 |website=The Sydney Morning Herald |access-date=September 19, 2012}}</ref><ref name="Engadget iOS 4 DST alarm fail">{{cite web|url=https://www.engadget.com/2010/11/01/iphone-dst-bug-causing-alarms-to-fail-across-europe |title=iPhone DST bug causing alarms to fail across Europe (updated)|date=November 1, 2010|website=Engadget|access-date=January 8, 2012}}</ref> It caused recurring alarms to start going off an hour too early or late. Apple promised the bug would be fixed in iOS 4.2/4.2.1, but according to some reports it still exists even in iOS 4.3.1.<ref name="Softpedia iOS 4 alarm bug">{{cite web|url=http://news.softpedia.com/news/iOS-4-3-1-Patch-Imperative-Battery-Drain-Alarm-Clock-Bug-Safari-Hole-189466.shtml |title=iOS 4.3.1 Patch Imperative – Battery drain, Alarm Clock bug, Safari hole|date=March 14, 2011|website=Softpedia|access-date=January 8, 2012}}</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}}</ref> However, two days after each New Year's Day, on January 3, 2011, they "magically" started working again. This bug was seemingly fixed in iOS 4.3.<ref name="Engadget iOS 4 alarm again">{{cite web|url=https://www.engadget.com/2012/01/01/psa-iphone-alarm-clock-not-working-again-time-to-update |title=PSA: iPhone alarm clock not working again? Time to update|date=January 1, 2012|website=Engadget|access-date=January 8, 2012}}</ref>

Line 50 ⟶ 51:

{{main|iOS 7#Problems}}

;Passcode screen bypass bugs

PeopleA arelock able toscreen bypass the "Enter Passcode" screen. This flaw was discovered within hours of it becoming publicly available. This is only able to be done on [[iPhone 5]] and earlier while the [[iPhonerelease 5C]]of andiOS [[iPhone 5S]] are safe from this bug. This is7, caused by the ability to use the [[Control Center (iOS)|control center]] viathrough the lock screen and tapping on the camera or timer buttons. ThisThe featurethen-latest iPhone models, the iPhone 5S and the iPhone 5C, were not affected. As a workaround, the Control Center can be turned off for the lock screen in the Settings app.<ref>{{cite web|url=https://www.theguardian.com/technology/2013/sep/20/apple-working-fix-ios-7-lockscreen-bypass-flaw |title=Apple says it's working on fix for iOS 7 lockscreen bypass flaw|date=September 20, 2013|website=Guardian News and Media|archive-url=https://web.archive.org/web/20130920222059/http://www.theguardian.com/technology/2013/sep/20/apple-working-fix-ios-7-lockscreen-bypass-flaw|archive-date=September 20, 2013|url-status=live|access-date=September 22, 2013|quote=Embarrassing discovery comes within hours of release of new software and exploits Control Center feature to hack into photos, texts and Facebook content}}</ref> This was fixed in iOS 7.0.2.<ref>{{Cite web|last=Gurman|first=Mark|date=2013-09-26|title=Apple releases iOS 7.0.2 with fix for Lock screen passcode bypass flaw|url=https://9to5mac.com/2013/09/26/apple-releases-ios-7-0-2-with-lock-screen-passcode-flaw-fix/|access-date=2021-01-30|website=9to5Mac|language=en-US}}</ref>

;Motion Sicknesssickness

Users complained about dizziness andmotion vertigosickness-like symptoms when using thisiOS operating system7 because of parallaxthe motionuser 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}}</ref>

;Creation of CardDAV Accounts not working

Creating a [[CardDAV]] Account contains a bug that needs manual fixing of the CardDAV-Server-URL.<ref>{{cite web|url=http://help.licobo.com/setting/sync/ios/ios7-carddav/?lang=en |title=licobo.com|access-date=October 22, 2015}}</ref>

;Battery drain problems

In iOS 7.1, users have reported seeing significant drain on their batteriesdevices' battery after installing the new update.<ref>{{cite web|url=https://9to5mac.com/2014/03/13/ios-7-1-makes-everything-faster-including-your-battery-drain/ |title=iOS 7.1 makes everything faster – including your battery drain|work=9to5Mac}}</ref>

;FaceTime

Issues with video-calling and connection errors. This was fixed in iOS 7.0.4. (See iOS 6.x)

;Safari ignores local ___domain

Local ___domain names can no longer be resolved in [[Safari (web browser)|Safari]].<ref>{{cite web|url=https://discussions.apple.com/message/23592318 |title=Safari ignores local ___domain|work=apple.com}}</ref><ref>{{cite web|url=https://discussions.apple.com/thread/5575236 |title=Safari can no longer address <host>.xxyyz... - Apple Support Communities|work=apple.com}}</ref> This breaks short names on the local network, e.g. 'nas' for nas.<ourdomain>.

;Home screen crashes

Users have reported various crashes of the home screen, the core service that renders the home screen icons, Notification Center, Control Center, Siri and the lockscreen.<ref>{{cite web|url=http://crave.cnet.co.uk/mobiles/apple-promises-to-fix-home-screen-crash-iphone-bug-50013288/ |title=Apple promises to fix 'home screen crash' iPhone bug|work=CNET}}</ref> This was fixed in iOS 7.1.

Line 69 ⟶ 68:

[[iPhone 4S]] users report experiencing problems with the battery indicator; the indicator will freeze at the same value until the iPhone is restarted again.<ref>{{cite web|url=https://discussions.apple.com/thread/5331165 |title=iPhone 4S battery indicator stuck after upgrade... - Apple Support Communities|work=apple.com}}</ref><ref>{{cite web|url=https://discussions.apple.com/thread/5104825 |title=battery indicator stuck at 1%|work=apple.com}}</ref>

;Touch ID

In iOS 7.1, [[Touch ID]] was not functioning on the [[iPhone 5S]]. The problem cannot be resolved by turning Touch ID on and off in the "Fingerprint and Passcode" menu, restarting, resetting, or restoring the device using [[iTunes]].<ref>{{Cite Thisweb|last=Prabhu|first=Gautam|date=2014-03-12|title=iPhone problem5s wasusers similarreporting toissues thewith Touch ID after [[iOS 8]].07.1 release, which crippled [[update|url=https://www.iphonehacks.com/2014/03/iphone-5s-touch-id-issue-ios-7-1.html|url-status=live|archive-url=|archive-date=|access-date=2021-01-30|website=iPhone 6Hacks|iPhonelanguage=en-US}}</ref> 6This andissue iPhonewas 6fixed Plus]]in of both cellular and TouchiOS ID7.1.1.<ref>{{Cite Thisweb|last=Kingsley-Hughes|first=Adrian|title=Apple was fixed inreleases 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}}</ref>

=== iOS 8 ===

{{main|iOS 8#Problems}}

;HealthKit

Shortly after the release of iOS 8, Apple released a statement pointing out that a bug had been found in the operating system which prevented HealthKit-compatible apps from being released alongside iOS 8.<ref name="HealthKit Bug">{{cite web|url=https://www.cnet.com/news/bug-forces-apple-to-delay-launch-of-healthkit-fitness-apps/ |title=Bug forces Apple to delay launch of HealthKit fitness apps|website=[[CNET]]|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 HealthkitHealthKit functionality were withdrawn from the App Store. iOS 8.0.1/8.0.2 included a fix for this issue.

;iOS 8.0.1

[[iPhone 6|iPhone 6 and iPhone 6 Plus]] users who updated to iOS 8.0.1 wirelessly had cellular service and Touch ID disabled due to a software issue.<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}}</ref> Over-the-Air downloads of iOS 8.0.1 were stopped within an hour of the release of the software,<ref>{{Cite web|last=Kingsley-Hughes|first=Adrian|title=Apple pulls iOS 8.0.1 update, after killing cell service, Touch ID|url=https://www.zdnet.com/article/apple-pulls-ios-8-0-1-update-after-killing-cell-service-touch-id/|access-date=2021-01-30|website=ZDNet|language=en}}</ref> but many early adopters had been affected. These issues were fixed with the release of iOS 8.0.2 a day later.

;Touch ID

Users who updated phones with Touch ID enabled to iOS 8.3 found out that they could not use Touch ID to make App Store purchases.<ref>{{cite web|url=http://wccftech.com/apple-released-ios-83-bug-fixes-features/ |title=Touch ID Fails in App Store With Apples Recent iOS 8.3 Release|date=April 9, 2015|newspaper=WCCFTech|access-date=April 12, 2015}}</ref> A workaround has been devised by users to repair this issue.<ref>{{cite web|url=http://wccftech.com/how-to-fix-touch-id-ios-8-3-bugs/ |title=How to Fix iOS 8.3 Touch ID Issue – iOS 8 Tips and Tricks|date=April 10, 2015|newspaper=WCCFTech|access-date=April 12, 2015}}</ref>

;Performance

Many users of older generation devices such as the iPhone 4s4S and the iPad 2 reported performance issues with iOS 8. Apple has since released iOS 8.1.1 in attempt to fix the problem.<ref>{{Cite web|last=Cunningham|first=Andrew|date=2014-11-04|title=iOS 8.1.1 said to address iPhone 4S and iPad 2 performance problems|url=https://arstechnica.com/gadgets/2014/11/ios-8-1-1-said-to-address-iphone-4s-and-ipad-2-performance-problems/|access-date=2021-01-30|website=Ars Technica|language=en-us}}</ref>

;Keyboard

Several issues with the new Keyboard API in iOS 8 were reported, including problems with custom keyboards crashing or not appearing, or being replaced with the default keyboard.{{Source needed|date=January 2021}} Apple has since released iOS 8.3 in attempt to fix the problem.

;iMessage

When a specific set of Arabic, Unicode, and English characters are sent through iMessage to an iOS device running iOS 8.0 or later, it causes the device to crash. This bug was discovered by a [[Reddit]] user in May 2015. Apple has since released a software update (iOS 8.4) to fix this issue.<ref>{{cite web|url=http://www.theinquirer.net/inquirer/news/2410183/ios-bug-lets-android-and-windows-phone-users-disable-your-iphones-messages-app |title=iOS 8.4 includes fix for iMessage bug plaguing iPhone users|work=theinquirer.net}}</ref>

Line 112 ⟶ 111:

Many users, especially those owning an iPhone 6s, reported that their phones would shut down automatically with 30% battery left.<ref>{{cite web|url=http://clark.com/technology/iphone-battery-drain-apple-bug/ |title=Mysterious bug is still shutting down iPhones with 30% battery left|date=January 25, 2017|work=Clark Howard|access-date=October 28, 2017}}</ref> This issue was fixed with the release of iOS 10.3.

As of the iOS 10.2.1 release, iOS throttles CPU performance on iPhones with batteries in poor health. ThisDue 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 release. As a result, Apple announced battery replacements would be $29 instead of $79.<ref>{{cite web|url=https://www.cnbc.com/2017/12/28/apple-batterygate-letter-full-text.html |title=Apple apologizes for iPhone slowdowns and offers $29 battery replacements|date=December 28, 2017|work=Anita Balakrishnan|access-date=January 24, 2018}}</ref> They also announced that iOS 11.3 would show battery health in the Settings > Battery menu and let the user decide if they wanted the previous 30% shutdown behavior or the throttled CPU.<ref>{{cite web|url=https://9to5mac.com/2018/01/24/ios-11-3-beta-1/ |title=Apple releases first iOS 11.3 Developer beta for iPhone and iPad|date=January 24, 2018|work=Zac Hall|access-date=January 24, 2018}}</ref>

=== iOS 11 ===

{{main|iOS 11#Problems}}

;Battery

Many users reported worse battery life with iOS 11 than with iOS 10.3.3.<ref>{{Citation |title=DO NOT install iOS 11 before Watching this Video|date=September 13, 2017|url=https://www.youtube.com/watch?v=WOHkKnRz4cI|access-date=October 28, 2017}}</ref> This issue was addressed with the release of iOS 11.1.<ref>{{cite web|url=http://bgr.com/2017/10/24/ios-11-1-battery-drain-fix-iphone-8/ |title=iOS 11 will dramatically improve battery life on all iPhones|date=October 24, 2017|work=BGR|access-date=October 31, 2017}}</ref>

;Calculator

Due to an animationa bug related to UI animation, quickly typing in an equation caused the built-in Calculator app to displaygive incorrect answers.<ref>{{cite web|url=https://www.macrumors.com/2017/10/24/ios-11-calculator-animation-bug/ |title=iOS 11 Bug: Typing 1+2+3 Quickly in the Calculator App Won't Get You 6|access-date=December 2, 2017}}</ref> The bug was fixed in iOS 11.2.

Due to an animation bug, quickly typing in an equation caused the built-in Calculator app to display incorrect answers.<ref>{{cite web|url=https://www.macrumors.com/2017/10/24/ios-11-calculator-animation-bug/ |title=iOS 11 Bug: Typing 1+2+3 Quickly in the Calculator App Won't Get You 6|access-date=December 2, 2017}}</ref> The bug was fixed in iOS 11.2.

;Mail

Line 127 ⟶ 122:

;AutoCorrect

Users complained of a bug in the built-in keyboard in iOS 11 that changed the letter "I" to "A [?]", if automatic correction was enabled.<ref>{{cite web|url=https://www.telegraph.co.uk/technology/2017/11/06/iphones-autocorrecting-letter-incomprehensible-symbol/ |title=iPhones are autocorrecting the letter 'i' to an incomprehensible symbol|date=November 6, 2017|work=The Telegraph|access-date=November 22, 2017}}</ref> This was fixed with the release of iOS 11.1.1.<ref>{{cite web|url=https://arstechnica.com/gadgets/2017/11/ios-11-1-1-is-here-it-fixes-the-autocorrect-bug-and-a-hey-siri-issue/ |title=iOS 11.1.1 is here: It fixes the autocorrect bug and a "Hey Siri" issue|work=Ars Technica|access-date=November 22, 2017}}</ref>

;December 2 respring

A bug in iOS 11 was present that would cause the device's tohome constantlyscreen respringto andconstantly crash if an app sends local notifications on or after 00:15 on December 2, 2017. Apple responded by releasing iOS 11.2 early, which fixed the bug.<ref>{{cite web|url=https://www.macrumors.com/2017/12/02/ios-11-1-2-date-bug-crash-loop/ |title=Date Bug in iOS 11.1.2 Causing Crash Loop on iPhones as December 2 Hits [Updated]|access-date=December 2, 2017}}</ref>

;Telugu character crash

A bug was present in iOS 10 and 11 that would cause an app to crash when a certain Telugusequence character(జ్ఞof ‌ా)Telugu characters was pasted into it, or for the phone's tohome respringscreen if pasted into Spotlight search.<ref>{{Citation |title=This Indian Text Will Crash ANY iPhone!జ్ఞ ‌ా|date=February 15, 2018|url=https://www.youtube.com/watch?v=K73fw99Xb9s|access-date=February 19, 2018}}</ref> The bug was fixed with iOS 11.2.6.<ref>{{cite web|url=https://9to5mac.com/2018/02/19/telugu-character-fix/ |title=Apple releases iOS 11.2.6, watchOS 4.2.3, tvOS 11.2.6, and macOS 10.13.3 supplemental update including Telugu character fix|date=February 19, 2018|work=9to5Mac|access-date=February 19, 2018}}</ref>

;iPhone 8 touchscreen issues after third -party repair

A bug withThe iOS 11.3 update caused some iPhone 8 devices that had had their screens repaired by a third party repair shop to become unusable by disabling the touch screen. Apple corrected this issue by releasing iOS 11.3.1.<ref>{{cite web|url=https://www.macrumors.com/2018/04/24/apple-releases-ios-11-3-1-update/ |title=Apple Releases iOS 11.3.1 Update With Fix for Third-Party Display Repair Issue}}</ref>

=== iOS 12 ===

Line 143 ⟶ 138:

;Group FaceTime Bug

{{main|FaceTime#Group FaceTime Bug}}

A privacy issue was discovered when using [[FaceTime]] in iOS 12.1. This, bugthat allowed users to [[eavesdrop]] the recipient with access to their camera and audio without them answering the call and their knowledge when adding another person to the call. As a result, Apple had permanently disabled Group FaceTime in iOS versions 12.1 to 12.1.3. An update was later released on 12.1.4 to fix the bug.<ref>{{Cite web|url=https://www.minicreo.com/ios-12-problems/|title='FaceTime Eavesdropping Issue' in iOS 12 |last=Woods |first= Kelly |date=24 May 2019|access-date=24 May 2019}}</ref>

;Sending iMessages to the wrong contacts

Line 149 ⟶ 144:

;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 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/|url-status=live|archive-url=|archive-date=|access-date=2021-01-30|website=iDownloadBlog.com|language=en-US}}</ref>

;iOS 12.4 jailbreak

Apple accidentally undid a fix to aA kernel codevulnerability executionthat exploitwas (Sockfixed Puppet)in thatiOS 12.3 was fixedaccidentally restored in iOS 12.34. This made iOS 12.4 vulnerable to exploits using the exploitvulnerability, 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}}</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}}</ref>

=== iOS 13 ===

==== 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}}</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}}</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/|url-status=live|archive-url=|archive-date=|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}}</ref>

;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. AppleThe quicklyissue was fixed this 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}}</ref>

=== iOS 14 ===

The initial release saw iPhone 11 Pro/11 Pro Max devices being rendered unusable if the battery was drained to zero; this has been corrected.

==== Missing keyboard for Spotlight search ====

The ability to change the default app for messages, email, internet or other services is reset to the default Apple app every time the iPhone, iPod or iPad is reset or turned off.

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|language=en}}</ref>

==== Battery issue on iPhone 11 Pro, iPhone 11 Pro Max ====

The initial release saw iPhone 11 Pro/11 Pro Max devices being rendered unusable if the battery was drained to zero; this has been corrected.{{Citation needed|date=January 2021}}

==== Default app setting reset ====

The iPhone keyboard did not appear for search.<ref>[https://www.tomsguide.com/news/ios-14-bugs-are-messing-with-apps-what-to-do-now iOS 14 bugs are messing with apps]</ref>

The ability to change the default app for messages, email, internet or other services is reset to the stock app every time the device is 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}}</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}}</ref>

==== General battery drain ====

On 30 September 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 and 6 other issues. In this document Apple claimed that unpairing the deviceiPhone withfrom syncedan Apple Watch followed by erasing all data and settings of the iPhone, and restoring from thea backup could be a possible fix for reviving the battery life.<ref>{{cite web|url=https://www.theverge.com/2020/10/2/21499243/ios-14-watchos-7-battery-drain-apple-iphone-watch-fix|title=If iOS 14 is causing battery drain, you might need to wipe your iPhone|access-date=2 October 2020|website=The Verge}}</ref>

== References ==