Content deleted Content added
Citation bot (talk | contribs) Alter: template type. | You can use this bot yourself. Report bugs here. | Suggested by AManWithNoPlan | All pages linked from cached copy of User:AManWithNoPlan/sandbox3 | via #UCB_webform_linked 159/687 |
m Task 18 (cosmetic): eval 64 templates: del empty params (4×); hyphenate params (35×); |
||
Line 8:
{{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 |
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|
=== iOS 5 ===
{{main|iOS 5#Problems}}
; Battery drain bugs
Apple confirmed that several battery life bugs were negatively affecting battery life in iOS 5.<ref name="Engadget iOS 5 battery bug">{{cite web|url=https://www.engadget.com/2011/11/02/apple-confirms-ios-5-bugs-causing-battery-drain-promises-a-fix |title=Apple confirms iOS 5 bugs causing battery drain, promises a fix 'in a few weeks'|date=November 2, 2011|website=Engadget|
;Wi-Fi
The launch of the iOS 5 update on October 12, 2011 (including iOS 5.0.1 released on November 10, 2011), led many users to report a major bug causing the device to lose [[Wi-Fi]] access. This problem has supposedly been fixed with the release of iOS 5.1.1<ref name="Engadget iOS 5 wifi bug">{{cite web|url=https://www.engadget.com/2011/11/21/thanks-to-ios-5-some-users-lose-wifi-connectivity |title=Thanks to iOS 5.1 some users lose Wifi connectivity|date=November 21, 2011|website=Engadget|
;SIM card
Some users of the iPhone 4S and iPad (Wi-Fi + Cellular) reported issues with the [[Subscriber Identity Module|SIM]] card in iOS 5.0,<ref name="AppleInsider SIM bug">{{cite web|url=https://www.appleinsider.com/articles/11/11/17/users_report_sim_card_issues_with_apples_iphone_4s_and_ios_5_0_1.html |title=Users report SIM card issues with Apple's iPhone 4S and iOS 5.0.1|date=November 17, 2011
;Echo bugs
Some users of the iPhone 4 and iPhone 4S reported issues with having echo problems during phone call in the initial release of iOS 5, which causes echoes to appear randomly during phone calls made through earbuds. The other party in the call is generally unable to hear the conversation due to this problem.<ref>{{cite web|url=http://www.bgr.com/2011/11/01/audio-echo-bug-plagues-iphone-4s-owners-during-voice-calls/ |title=Audio echo bug plagues iPhone 4S owners during voice calls
=== iOS 6 ===
{{main|iOS 6#Problems}}
;Maps
Apple has admitted that there were several bugs in the mapping app on [[iOS 6]], with cities in the wrong ___location, some places being missed off altogether, some places misnamed and places of interest in the sea.<ref name="Letter from Tim Cook on Maps">{{cite web|url=https://www.apple.com/letter-from-tim-cook-on-maps |title=Letter from Tim Cook on Maps|archive-url=https://web.archive.org/web/20121001014531/http://www.apple.com/letter-from-tim-cook-on-maps|archive-date=October 1, 2012}}</ref><ref name="compweekly map errors">{{cite web|url=http://www.computerweekly.com/news/2240163685/Apple-admits-iPhone-5-Maps-app-needs-fixing |title=Apple admits iPhone 5 Maps app needs fixing|
;Bluetooth
Many users report a problem with Bluetooth audio streaming to a range of compatible devices. The sound cuts out every now and then for no apparent reason. {{As of|2012|10}}, no solution has been provided by Apple.<ref>{{cite web|url=https://discussions.apple.com/thread/4318307?start=0&tstart=0 |title=iOS 6 Bluetooth problems}}</ref>
Line 32:
Location-based reminders do not work for iPads, even though they were promised to work on cellular enabled devices.<ref>{{cite web|url=https://discussions.apple.com/thread/4311603 |title=Will Location based reminders work on ios 6 for the IPad 3 I keep getting a message that siri can't do ___location based reminders on this device any help please}}</ref> It has later been clarified by Apple that only the 4th generation iPad and the iPad Mini 1st generation or later will be able to use this.<ref>{{cite web|url=https://support.apple.com/en-gb/HT202335 |title=Create and use Reminders on your iPhone and iPad - Apple Support}}</ref>
;Cellular Network
In iOS 6.1, users reported problems with cellular connectivity. This was addressed for the iPhone 4S in iOS 6.1.1 which "fixes an issue that could impact cellular performance and reliability for iPhone 4S."<ref name="PCmag 4S bugs">{{cite web|url=https://www.pcmag.com/article2/0,2817,2415311,00.asp |title=Apple Rolls Out iOS 6.1.1 to Fix iPhone 4S Bugs|date=February 11, 2014|work=PC Magazine|
;Do Not Disturb
Many iPhone users experienced a bug with the Do Not Disturb feature when the calendar changed from 2012 to 2013. The feature would be left on past the scheduled time set by the user, allowing texts, notifications, and alarm settings to be missed. The bug was caused by a difference in formatting in the [[ISO 8601|ISO calendar]] system versus the [[Gregorian calendar]] system.<ref>{{cite web|url=https://arstechnica.com/apple/2013/01/ask-ars-why-will-apples-do-not-disturb-bug-fix-itself-next-week |title=Ask Ars: Why will Apple's Do Not Disturb bug fix itself next week?|date=January 3, 2013|
;Microsoft Exchange
Another bug causes issues when iOS devices connect to a Microsoft Exchange server to retrieve email, resulting in message "mailbox server resources are consumed, log growth becomes excessive, memory and CPU use may increase significantly, and server performance is affected".<ref name="theverge MS Exchange bug">{{cite web|url=https://www.theverge.com/2013/2/12/3981682/microsoft-investigating-ios-6-1-exchange-sync-problems |title=Microsoft suggests throttling or blocking iOS 6.1 devices after bug slows down Exchange servers|date=February 12, 2013|
;Lockscreen bypass code
On iPhones, another bug found in 6.1 allowing bypassing the lock screen's passcode to temporarily gain full access to the Phone app, by performing a specific sequence of actions on the phone that remained unfixed,<ref name="Gizmodo 6.1 phone bypass">{{cite web|url=http://www.gizmodo.co.uk/2013/02/you-can-bypass-the-ios-6-1-lockcode-screen-with-this-simple-technique |title=You Can Bypass the iOS 6.1 Lockcode Screen With This Simple Technique|date=February 14, 2013|
;Audio profile speakerphone
[[iPhone 5]] users experienced dropped calls during the release of iOS 6.1.3 when there was an issue with the audio [[microphone]] profile. This also caused issues with many voice-over commands, including [[Siri]], to get different results than expected or to fail easily. Apple fixed this bug with the release of iOS 6.1.4, which updated the audio speaker profile so users would get better results.
;FaceTime
Shortly after Apple released [[iOS 7]], users running iOS 6 were said to have problems using FaceTime. Apple later released a support document stating that this was due to an expired device certificate and that devices that support iOS 7 should update to it in order to resolve these issues.<ref name="ftbug">{{cite web|url=https://www.macrumors.com/2014/04/24/ios-6-facetime-fix/ |title=iOS 6 Users on Devices Able to Run iOS 7 Must Upgrade to Fix FaceTime|date=April 24, 2014|
;Data security
An attacker can collect or modify data in sessions protected by [[SSL/TLS]] protocols. This same bug was also reported on iOS 7.0.4 and iOS 7.0.5 for the iPhone 5C and 5S. For the [[iPhone 3GS]] and the [[iPod Touch (4th generation)]], iOS 6.1.6 was released to fix this issue since iOS 7 is not compatible with these devices (see iOS 7.x).
Line 50:
{{main|iOS 7#Problems}}
;Passcode screen bypass bugs
People are able to bypass the "Enter Passcode" screen. This flaw was discovered within hours of it becoming publicly available. This is only able to be done on [[iPhone 5]] and earlier while the [[iPhone 5C]] and [[iPhone 5S]] are safe from this bug. This is caused by the ability to use the [[Control Center (iOS)|control center]] via the lock screen and tapping on the camera or timer buttons. This feature can be turned off in the Settings app.<ref>{{cite web|url=https://www.theguardian.com/technology/2013/sep/20/apple-working-fix-ios-7-lockscreen-bypass-flaw |title=Apple says it's working on fix for iOS 7 lockscreen bypass flaw|date=September 20, 2013|website=Guardian News and Media|
;Motion Sickness
Users complained about dizziness and vertigo-like symptoms when using this operating system because of parallax motion effects.
In iOS 7.1, a new function in the Settings app named "Reduce Motion" was introduced to reduce the motion of the user interface and disable the parallax effects.<ref>{{cite news|title=How Apple's iOS 7.1 finally quelled users' motion sickness|author=Craig Grannell|newspaper=The Guardian|date=March 13, 2014|url=https://www.theguardian.com/technology/2014/mar/13/apple-iphone-ipad-ios-71-motion-sickness}}</ref>
;Creation of CardDAV Accounts not working
Creating a [[CardDAV]] Account contains a bug that needs manual fixing of the CardDAV-Server-URL.<ref>{{cite web|url=http://help.licobo.com/setting/sync/ios/ios7-carddav/?lang=en |title=licobo.com|
;Battery drain problems
In iOS 7.1, users have reported seeing significant drain on their batteries after installing the new update.<ref>{{cite web|url=https://9to5mac.com/2014/03/13/ios-7-1-makes-everything-faster-including-your-battery-drain/ |title=iOS 7.1 makes everything faster – including your battery drain|work=9to5Mac}}</ref>
Line 74:
{{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]]|
;iOS 8.0.1
[[iPhone 6|iPhone 6 and iPhone 6 Plus]] users who updated to iOS 8.0.1 wirelessly had cellular service and Touch ID disabled due to a software issue. Over-the-Air downloads of iOS 8.0.1 were stopped within an hour of the release of the software, but many early adopters had been affected. These issues were fixed with the release of iOS 8.0.2 a day later.
Line 90:
;Game Center
Many users reported greatly increased [[Game Center]] loading times which in turn caused apps that used Game Center logins to appear to load slowly.<ref>{{cite web|url=https://www.cultofmac.com/390755/beware-this-fix-for-nasty-ios-9-game-center-bug/ |title=Beware this 'fix' for nasty iOS 9 Game Center bug|website=Cult of Mac|
;January 1, 1970
Line 101:
;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|
;Security
Line 117:
{{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|
;Calculator
Line 134:
;Telugu character crash
A bug was present in iOS 10 and 11 that would cause an app to crash when a certain Telugu character(జ్ఞ ా) was pasted into it, or for the phone to respring if pasted into Spotlight.<ref>{{Citation |title=This Indian Text Will Crash ANY iPhone!జ్ఞ ా|date=February 15, 2018|url=https://www.youtube.com/watch?v=K73fw99Xb9s|
;iPhone 8 touchscreen issues after third party repair
A bug with iOS 11.3 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
=== iOS 12 ===
Line 143:
;Group FaceTime Bug
{{main|FaceTime#Group FaceTime Bug}}
A privacy issue was discovered when using [[FaceTime]] in iOS 12.1. This bug allowed users to [[eavesdrop]] the recipient with access to their camera and audio without them answering the call and their knowledge when adding another person to the call. As a result, Apple had permanently disabled Group FaceTime in iOS versions 12.1 to 12.1.3. An update was later released on 12.1.4 to fix the bug.<ref>{{Cite web|url=https://www.minicreo.com/ios-12-problems/|title='FaceTime Eavesdropping Issue' in iOS 12 |last=Woods |first= Kelly |date=24 May 2019|
;Sending iMessages to the wrong contacts
iOS 12 merges conversation history for devices using a shared Apple ID, even if separate handles are used, such as unique phone numbers or email Fixes. As a result, iMessages may be delivered to the wrong device.<ref>{{cite web|url=https://mashable.com/article/apple-ios-12-merged-messages-wrong-contacts |title=Apple users claim iOS 12 is sending iMessages to the wrong contacts |website=Mashable |
;iOS 12.3.2 update incompatibility
Line 166:
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>
On 30 September 2020, Apple acknowledged battery drain issue in iOS 14 and released a supporting document that offered the users tricks to fix the poor battery performance and 6 other issues. In this document Apple claimed that unpairing the device with synced Apple Watch followed by erasing all data and settings, and restoring from the backup could be a possible fix for reviving the battery life.<ref>{{cite web|url=https://www.theverge.com/2020/10/2/21499243/ios-14-watchos-7-battery-drain-apple-iphone-watch-fix|title=If iOS 14 is causing battery drain, you might need to wipe your iPhone|
== References ==
| |||