Requirement to enter passcode every 48 hours

No, it's a bug, an unwelcome "feature" inadvertently introduced in iOS 9. I can't imagine anyone in their right mind working at Apple had intended for the user to have to re-enter their password every two days, when they've been unlocking their device continually with Touch ID, including numerous times within the previous 48 hours. That makes no sense. So, it is a bug, and Apple is demonstrating that they are still struggling in the Q/A department, likely due to Wall Street's insatiable demands that Apple release new stuff on an impossible schedule.

IVe had this issue on my iPhone 6 every two or three weeks while my husband has not had this error yet!! He's got an iPhone 6 Plus same software.

HOwever, sometimes his finger doesn't work to answer his phone calls. Rather annoying!

There is no way I am going to read 11-pages of forum posts and try to sift through it all... so please pardon my asking: Has there been a definitive solution to this phenomenon or is it still an ongoing issue awaiting a fix from Cupertino...?

I have had this happen on my iPhone 6, my iPad, my iPad Pro... and as of 2 days ago, my WIFE had it happen on HER new iPad.

It's clearly a bug - and I am about to log a feedback message to Apple, but figured I'd look for a solution on here first. A quick glance at pages 10 & 11 seem to signal that there is no solution yet, but I may be mistaken. Thanks.

After the "48 hour bug" began hitting my iPhone 6 Plus more frequently, and noticing some UI irregularities in everyday use, I did a complete restore and setup as new iPhone yesterday. I didn't use iTunes. It took hours to get the phone back where I wanted it, naturally, and due to the nature of this bug, I'll never be 100% certain if it's gone. I guess if it doesn't rear its head again prior to the next iOS update, that would be an indication. Got mah fangers crossed. Happy Holidays to all!

same problem here, but i noticed that not always happen, sometime message appear after i charge my phone and sometimes during the day when i use it.

i try to open a chat session with apple but i get this message CAS.error.CASWS-INPUT-VAL-01 e56cee1d-6261-4093-a0e7-9dcfb294a2dc, anyone have any clue what is this about ? this appears on microsoft edge

Seveen wrote:

same problem here, but i noticed that not always happen, sometime message appear after i charge my phone and sometimes during the day when i use it.

It is a bug in iOS

i try to open a chat session with apple but i get this message CAS.error.CASWS-INPUT-VAL-01 e56cee1d-6261-4093-a0e7-9dcfb294a2dc, anyone have any clue what is this about ? this appears on microsoft edge

Use a supported web browser.

You can forget resetting and fresh install...

Spent 4 hours November 17 doing factory reset & reinstalling IOS 9.1 on iPhone6,1 5s

and already getting daily crash of CoreTime happening at 19:00-19:10

Phone fills with numerous crash logs !

Even "Share with Developers" is enabled but no word of any effort to remedy or acknowledgment of receipt.

And again got 48 hour request for PIN after using up to midnight or 7 hours prior.

SOMEBODY SHOULD FIND PROBLEM AND FIX THIS !

Maybe tell the media to start reporting on this and get some attention.

Cool Games wrote:

SOMEBODY SHOULD FIND PROBLEM AND FIX THIS !

Maybe tell the media to start reporting on this and get some attention.

Better yet, contact Apple Support!

-> https://www.apple.com/support/iphone/

Pretty sure the media can't fix this.

While irritating and inconvenient, this bug is hardly worth the "alert the media" cry. There are far-more-important bugs and fixes for developers to squash and this one doesn't warrant an NBC News story.

🙂

I am sure this will be dealt with in the next point-release. Until then, we just simply re-enter our passcodes.

I was just wondering if I had a "setting" somewhere set wrong - but seeing that this is an iOS bug... and Apple HAS been notified... it will be prioritized and dealt with when they get to it.

EDIT: And I cannot imagine this hasn't happened to developers and/or executives *AT* Apple as well. 🙂

I too have had this problem for the first time this morning. I upgraded to the latest iOS version a couple of weeks ago and constantly use my phone for personal use. I don't have exchange and don't have any profiles on my device. I'd never go 48 hours without unlocking my phone yet the message appeared this morning for the first time. This has to be a bug but I can't think what I've done differently to trigger it.

This is a serious bug that needs fixing Asap ......... Forcing the use of a low tech unsecure solution over a high tech biometric solution is a hackers dream come true !

GET IT FIXED URGENTLY Apple please

At the very least, this type of a bug should be terribly embarrassing for Apple. Awash with cash, while offshoring development and taxes to maximize Wall Street's pleasure, it seems that Apple could easily afford to beef up the Q/A efforts. This is a broken feature. The touch ID login, which is supposed to shield the passcode from eavesdroppers' eyes, fails to operate at any random time, for a VERY large population of users with touch ID based phones. Look at the sales numbers for iphone 6 and 6s versions...all those users with relatively new iphones, who depend on touch ID for a little extra security, in a world rich with technology security breeches, are now a little less secure, due to Apple's shoddy effort at quality control.

IIt's been over 2 weeks since the bug had reared its head for me. Prior to this, it would crop up almost daily. Of course, this isn't due to my cleverness; it just seems to have gone away, for now at least.

And guys, go easy on the folks who come here to rant a bit and blow off some steam. what they don't need is to be told that they are overreacting and that they need to calm down. With Apple being so inaccessible, its cathartic to know that others are frustrated, so let them have their moment, and maybe even be a little sympathetic If you can muster it.

(That last paragraph wasn't directed at anybody in particular so please nobody get your propeller beanies spinning over this.)

There are several bugs in iOS that need to be fixed. Each one takes time, and fixing each one has the added risk of having side effects. So it is essential to prioritize where to direct energy in fixing bugs. It is not possible to fix every bug in zero time, or even one bug in zero time, because every change to code affects over a half billion iOS devices, and any slip-up can potentially break that number of devices. This bug is one example of that. The view that "My bug is the worst thing in the world and it must be fixed immediately!" is selfish and unrealistic.

This is not a serious bug. It does not compromise security of the device. If anything, Touch ID weakens the security of the phone. It has been spoofed. And for anyone who feels that the government should not have access to their data it is foolish to even use it, because courts have ruled that, while you can refuse to provide your passcode to law enforcement, you cannot refuse to unlock your device with your fingerprint. It's only advantage is convenience, not security.

Compare this bug to one that has been around for a couple of months - Mail received on the phone from POP accounts all disappeared when iOS 9 was installed. It is unrecoverable. And new mail received on POP accounts disappears after a couple of days.

Which do you think is more serious?

Please read my post before jumping to several incorrect conclusions.

The point to the bug is that enforcing a less secure login in this security critical day is a very bad thing.

We didn't have apple pay until recently and this alone requires significant ramp up of phone security.

BTW the fact that a fingerprint cannot be changed is a strength not a weakness as you suggest as it cannot be changed by a hacker

4 digit pin is least secure, alpha numeric password more secure and biometric print most secure.