Q: Requirement to enter passcode every 48 hours
-
Nov 14, 2015 4:10 AMby Doddsyuk,there is no pattern to it, it's random, just because you haven't had the issue since you soft reset your phone doesnt mean it's a fix, others have reported trying this and it still happens. Based on your logic, I could say doing nothing is a fix cos since I did nothing to try and fix it the other day it hasn't happened since.
I would say the most likely cause of this is some incorrect logic in the code that decides that it's 48hrs since you used your phone and the fix will be a software update.
-
Nov 14, 2015 4:43 AMby _RomMon,
Just to mark this for reference.Observed this behavior as well today for the first time (realizing it probably happening for a bit longer).
I have only read a little of this thread (just the first two pages, and last two partially).
(did install a few apps involving touch ID support, (e.g. Paypal) is that related?)
-
Nov 16, 2015 5:10 PMby Ubisububi,I too, am having this problem on my iPad, although it's not happening on my iPhone. It started very recently after one of the OS9 patches. It is not due to a profile or a work-related email account (I am retired so no work content on either device). Lastly, although mine is only a 4-digit passcode, it's still annoying and not working as intended.
<Edited by Host>
-
Nov 16, 2015 5:17 PMby Lawrence Finch,Ubisububi wrote:
I too, am having this problem on my iPad, although it's not happening on my iPhone. It started very recently after one of the OS9 patches. It is not due to a profile or a work-related email account (I am retired so no work content on either device). Lastly, although mine is only a 4-digit passcode, it's still annoying and not working as intended.
- It's not an iOS 9 problem, because people reported it with iOS 8.4 (in this very thread)
- It isn't due to a profile on YOUR PHONE, but it very well could be for other users
- Yes, it's annoying
- Yes, it is not working as intended.
Is there anything else to discuss about it? All of the reasonable troubleshooting attempts have already been posted in this thread, and none of them have solved it.
Regarding the "annoying" factor, in every software product there are bugs. One of the jobs in managing bugs is triage. A way of thinking about bugs is to classify them. A company I worked for used four levels:
- Critical: The function is unusable
- Severe: The function is unusable as intended, but has a workaround, or it's possible to live with it in a degraded mode
- Annoying: The function works, but in a way that makes extra work for the user
- Interesting: It's an oddity that doesn't cause any harm, but it shouldn't work that way
Apple has many more levels than this, but the principle is the same. Deal with the Critical and Severe bugs first; fix the Annoying and Interesting as time permits. This one isn't stopping anyone from using their phone. There have been bugs with iOS 9.0 that DID prevent people from using their devices. iOS 9.0.2 fixed that one, very quickly. There is a current Severe bug that affects millions of people, but does have a workaround: email messages from POP accounts lose their content a few days after receipt and display "this message has not been downloaded from the server." Users have lost years of email history, unrecoverably. The workaround is to use an email app from the app store, instead of Apple Mail. The fix for that has not been released yet, but hopefully will be Real Soon Now. I'm sure the "48 hour" issue will be fixed, but it isn't as high a priority because it doesn't prevent anyone from using their phone or iPad and doesn't interfere with a critical function of the phone. -
Nov 16, 2015 5:39 PMby Ubisububi,Sorry...
I agree with you. There is nothing more to discuss. I was just frustrated when I tried to read through this thread and found it clogged with so many useless posts by the same guy.
I'm surprised that this is not an iOS 9 issue, though. Thanks for that insight.
-
Nov 17, 2015 1:07 PMby Cool Games,Any one look at diagnostics.
I get lots of Core Time crashes.
And I just needed to enter pass code before 48 usage but no crash was reported so I may be off target.
Now on IOS 9.1 so this last message not current IOS.
Diagnostics are at Settings > Privacy > Diagnostics & Usage
I am not a developer so also no clue what it means.
{"os_version":"iPhone OS 9.0.2 (13A452)","bug_type":"156","timestamp":"20151011 20:13:11.11 0400"}
Date:20151011201311
Incident ID:A39E2FB8E631437BA6B36DA1AE6B6A32
Hardware Model: iPhone6,1
OS Version: iOS 9.0.2 (13A452)
System ID:
20151010 20:11:38 0400 timed[58]: type:21;rtc_s:65688683.530395;mach:945837263115
-
Nov 17, 2015 2:06 PMby Cool Games,As per Apple Chat...
Seems to indicate restore only after ERASE DEVICE and add Setup Assistant.
I am trying the Backup then Restore with iTunes 12.3.1.23 on El Capitan 10.11.1
Wish me luck !
"Marcus:
I would suggest to attempt to restore the device. To restore using iTunesConnect your device to the computer that you stored your backup on. Open iTunes. Click restore and wait for the process to finish. The only way to restore from an iCloud backup is through the Setup Assistant. To get to the Setup Assistant on a device you already set up, you'll need to erase all the content on your device(Opens in new window)(Opens in new window) and set it up again."
-
Nov 19, 2015 3:32 AMby PEsteves,I too join all of you... it happened to me this morning when I got up. The last unlock on my iPhone 6 was about 8 hours earlier... am on 9.1 and it is a private phone with no other profile hang ups. One worry is whether it could be malware or an external request to go past the security of the phone? This is my worry, can manage the bug if it is really a bug till it is sorted.
