Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

"Require Passcode: Immediately" is my only option

I believe this is intentional. Since the fingerprint sensor makes it very fast and convenient to unlock the phone, if you decide to lock the phone it will default to "require immediately" since unlocking is almost seamless.
 
deadwalrus said:
It's still extra steps. Unlike unlocking from sleep, where your thumb is already resting on the home button, this needlessly creates friction. It kills the purpose of the swipe-to-unlock.

/rant
Click to expand...

Why unlock from sleep? a quick press of the home button won't activate Touch ID.
 
cwosigns said:
Why unlock from sleep? a quick press of the home button won't activate Touch ID.
Click to expand...

That's not what I meant. When the phone is sleeping and you want to get into it, touch ID makes perfect sense because you have to push the home button anyways and so your thumb is already resting on it.

When "swipe to view" an email or text message, your thumb is on the screen swiping left to right. Then you are forced to moe your thumb to the home button and unlock with touch ID. And then it fails once or twice. It's very frustrating that they removed the option to give it a minute or two before it requires authentication to get back into the device.

----------
joshdammit said:
It sounds like you have a really hard life.
Click to expand...

Yes Apple is perfect. No one wants the options they removed.

Thanks for the lecture.

----------
cwosigns said:
You can swipe to respond. Swipe the notification that you want to respond to,then put your finger on the home button to use Touch ID.

EDIT: I see this has been covered. But really...it's not that big of a deal. Apple introduces a piece of technology that is implemented far better than anyone has ever done on a mobile phone, and people are whining because they have to rest a finger or thumb on their phone for .5 seconds to unlock their phone?

I'm not sure I have words to describe how crazy that sounds.
Click to expand...

Again, thanks for the lecture. I've acknowledged that Touch ID works great. It's just frustrating that they removed an option that people used for no real reason.
 
Just wanted to chime in...

I love touch id.

But I do find it inconvenient, when I get a text lets say, if my iPhone is locked and in my pocket. I get a sound that I got a text. It is very unnatural to swipe the text notification left to right. And then put my thumb on the home button.

One thing I find funny is people's comments on the inconvenience making lite of it. I find it weird one of the selling points of touch id is its convenience, along with security. That is part of what makes it great, when you press the home button you just leave your finger there for a split second and it unlocks your phone.

So when an aspect of touch id is inconvenient, than people say get over it or turn it off.

Anyway like I said I love touch id. I would still have the setting set to immediate. I don't know the answer to make swiping notifications more fluid and natural. Just my 2 cents...
 
If you are on conference calls where you have to mute, someone will ask you for information and you have to touch-ID and unmute. This takes a second and is very unnatural, as it sometimes does not revert to the phone screen. During an active call, if you background the call, then lock, it does not automatically come back to the phone call. Very, very annoying, as then you can't unmute and people think you've dropped the call.

To the people who say, "well then don't background your calls and then lock", piss off. This workflow is completely unnatural. Waiting patiently for a jailbreak to fix this.
 
This is why I just bought a used 64gb 5 over a 32gb 5S.

I don't care about slightly better camera or the yet-to-be-unleashed-by-software added raw power and 64bit CPU. (what I was interested in was Safari performance and in some side-by-side tests on youtube I had even seen the 5 loading some pages faster than the 5S, and generally be on par)

What I cared about was the added convenience of TouchID.

Actually I didn't know about this thread and about this issue (which I think has a good chance to be fixed in the coming software updates, Apple can still stand by the fact that it makes sense to DEFAULT to immediately but give savvy people other options), what I DID know was that most of the times I take my iphone out the pocket I unlock it by swipe-to-view (or swipe-to-app as I call it) and muscle-memory 4 digit code ON THE SCREEN ITSELF. I don't have to move my attention and thumb to the lower part of the phone where the home button is. That'd be added friction. deadwalrus worded it perfectly:

deadwalrus said:
That's not what I meant. When the phone is sleeping and you want to get into it, touch ID makes perfect sense because you have to push the home button anyways and so your thumb is already resting on it.

When "swipe to view" an email or text message, your thumb is on the screen swiping left to right. Then you are forced to moe your thumb to the home button and unlock with touch ID. And then it fails once or twice. It's very frustrating that they removed the option to give it a minute or two before it requires authentication to get back into the device.
Click to expand...

What I hope for the future is someone coming up with a way to read your finger directly on the touchscreen WHILE you swipe-to-app.
Since the current touchID is based on capacitive-reading (not optical scanning), it's not entirely unfeasible to imagine that, if the the whole screen had a super high resolution capacitive digitizer, if that even makes sense. Of course that could also be applied to Macbook touchpads and Magic touchpads for authentication on Macs.
 
I have this same problem.

It was solved by choosing the fingerprint ID for app purchases only and not the unlocking of the iPhone...I'm not sure why this happened when I had preciously been able to set a time. Maybe it's a bug or maybe the rules changed?

I prefer to keep my iPhone unlocked at home and locked when I leave the house. I hope tho that this function will be fixed or rendered to return to the precious options.

Does anyone else have any updates on their issue with this?
 
It's not a problem it is working as intended. Your only option is to do what what you did or put up with it and hope Apple add the option in the future.
 
I find it a hassle as well. Hopefully they change it. Ive since disabled the fingerprint sensor. The novelty has worn off for me as it has made accessing my phone less practical.
 
Lets hope a jailbreak-tweak can fix this? Anyone mind posting a request @ reddit or something? :D
 
I'm sorry to resurrect an old thred, but not having a delayed lock option with touch ID is extremely annoying. I hope Apple changes this with an update sometime soon.

And yes, I've already left feedback.
 
MacOG728893 said:
I'm sorry to resurrect an old thred, but not having a delayed lock option with touch ID is extremely annoying. I hope Apple changes this with an update sometime soon.



And yes, I've already left feedback.
Click to expand...


Yep it's extremely annoying. Apple won't change it though.
 
May I ask what is annoying? For me Touch ID is so sensitive I can never see the lock screen when pressing the home button. It immediately unlocks. Why would a delay be needed?
 
Paco II said:
May I ask what is annoying? For me Touch ID is so sensitive I can never see the lock screen when pressing the home button. It immediately unlocks. Why would a delay be needed?
Click to expand...

I think you are confused with the term "delayed lock." This refers to a period of time after the screen has gone off that the phone will remain unlocked and thus, not require a code or Touch ID.

For instance, when I had an iPhone 5, I used a pass code for security. The key difference is that my pass code would only be required after 15 minutes of inactivity. This is useful for when you are engaged in a conversation of some sort and would like to swipe directly to that message.

This is still available with the my iPhone 6 and iOS 8, however, only if one uses the pass code method. If someones chooses to use Touch ID, this option is not available.

Anyways, I am so annoyed with this, I might just use the pass code alone with a delayed lock instead of Touch ID until it's implemented.

----------
617aircav said:
Yep it's extremely annoying. Apple won't change it though.
Click to expand...

Why do you feel that?
 
"Require Passcode: Immediately" is my only option

No I understood. But if the phone immediately unlocks upon wake when using Touch ID, what is the need for a delay?

Edit to add: does Touch ID not work well for you? When you press the home button to wake the phone, doesn't it immediately wake and unlock as it does for me?


MacOG728893 said:
I think you are confused with the term "delayed lock." This refers to a period of time after the screen has gone off that the phone will remain unlocked and thus, not require a code or ...
Click to expand...
 
Paco II said:
No I understood. But if the phone immediately unlocks upon wake when using Touch ID, what is the need for a delay?

Edit to add: does Touch ID not work well for you? When you press the home button to wake the phone, doesn't it immediately wake and unlock as it does for me?
Click to expand...

Yes, but if you have multiple notifications than it makes for less than an ideal experience. Wake with home button>swipe to notification I want>put finger back down.

This becomes really annoying when multiple notifications are coming in for different apps and you're constantly turning on and off your screen.

Also, touch ID generally opens you to the home screen or last app used. That's what I use swipe on a specific notification in the first place.

Edit: You can disagree with all of this and that's fine. Different strokes for different folks, but that's why we have options.. or should have options.
 
Now that I better understand your work flow I actually do not disagree. That would be annoying.
 
bobsaget123 said:
Hah JohnD3 did all of that, with no luck. At least it may seem this is an early bug and is not just affecting me... Hopefully it will be sorted out sooner rather than later.
Click to expand...

This isn't a bug. It's a requirement of most Microsoft Exchange email accounts that you have a passcode set up on your device. Check your email accounts and bet one of them is an exchange account.

My work email is the prime example; with it set up on my phone I have to use a passcode and can't change the lock time, without it set up, I can do as I please. I'm surprised there's there's no official documentation explaining this. On android, exchange accounts literally have the power to lock, locate and erase your device remotely. My webmail portal even has a section for doing so.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back