Requirement to enter passcode every 48 hours

As Apple doesn't read this user-to-user forum, no one at Apple can tell you anything here.

RMSko wrote:

I too charge my phone every night. It's only happened three or so times for me, but when it has happened, it was only in the morning after the phone has charged all night. No idea whether that's a coincidence, but it is a fact.

It's coincidence. It has happened to me at times other than the first wake-up in the morning. It's happened 3 times on my iPad, which I do NOT charge overnight, and once on my iPhone, which I do charge overnight. However, it happened during the day after I had used it several times.

Stumbled on to this thread searching for why this is happening to my iPad. Luckily, I don't think I've seen this happen on my phone but its frequent with the iPad. Similar to you and others, I charge phone ever night, iPad every few days. Didn't see much help/answers in this thread (but a LOT of flaming! which I can't see I see too much of on Apple boards!)

Hope we get a fix or a solution soon!

I've also seen this issue today. I'm on iOS 9.1 now on iPhone 6 plus.

iPhone says it needs passcode to unlock after not being unlocked for more than 48 hours with touch ID... This is untrue as I unlocked it an hour ago.

So clearly a bug in iOS 9 ? I'm not attached to any exchange or corporate account. I know the 48 hours thing is a feature when using Touch ID; but it's only supposed to kick in if you dont unlock the phone for 2 days....

iZian wrote:

So clearly a bug in iOS 9 ?

Yes it appears to be a bug in iOS 9.

it hasn't happened to me for a week now. On any of my 3 devices on iOS 9.1

Stopped happening on my iPhone 6 Plus for the past two weeks, after doing it each of the prior two weeks, but it just occurred last night on my iPad air 2. I use both these devices every day, using the touch id to log in. There is definitely a bug in iOS 9.1, perhaps even was present in 9.0. I never had this happen pre-9.1, and I've had my iPhone 6 plus for just over a year, the iPad air 2 for a couple of months. Both are running 9.1. Still wondering where Apple outsources this development to...Apple is starting to look more and more like Microsoft. Would sure like Steve Jobs back at the helm, to take no prisoners when it comes to demanding higher quality. The current guy at the top just doesn't seem to have that figured out, not sure he ever will.

Yes, I would concur, it is absolutely an Apple bug in iOS 9.x. The only guessing involved is whether it was first introduced in 9.0 or 9.1.

technonut wrote:

The only guessing involved is whether it was first introduced in 9.0 or 9.1.

Considering the first report of this issue in this thread was 3 weeks prior to 9.1 release (iOS 9.1 released on 21 October 2015), we can conclude it was NOT introduced with 9.1.

It was 9.0, 9.01 or 9.02.

Indeed, and people in this thread even mention their version.

I had the issue on 17th October with 9.0.2, and it happened this morning on 1st November with 9.1

Very frustrating as I use a very long mixed character/special character password to maximise the benefit of the fingerprint authentication.

-- Pete

Having to enter the password is annoying enough but what is really bugging me is not being able to enter the password and having to do a hard reset to get into my phone each time it happens. Is anyone else finding the on screen keyboard doesn't work when it locks?

what's the solution to this 48 hour problem. It happened to me again this morning. No reason.

Anne Mc wrote:

Is anyone else finding the on screen keyboard doesn't work when it locks?

No, I've not seen that problem, or even other reports of it.

I have had this happen to me as well. It was always when I would unlock the

phone first thing in the morning. It is not commonly happening (4 times in the past

month). I never had the keyboard lock up and was able to enter the passcode.

I don't think it mattered whether it was charging over night or not.

I have a 6S that I got at the end of September, so it has happened over the span

of the updates.

Chris CA wrote:

Considering the first report of this issue in this thread was 3 weeks prior to 9.1 release (iOS 9.1 released on 21 October 2015), we can conclude it was NOT introduced with 9.1.

It was 9.0, 9.01 or 9.02.

Correct, it happened to me on all those levels intermittantly and unfortunately is it not fixed with 9.1 either as it happened there as well yesterday morning.