LAContext localizedFallBack option is being ignored in iOS 8.3

Originator:jorge
Number:rdar://20653405 Date Originated:04/22/2015
Status:Open Resolved:
Product:iOS Product Version:8.3
Classification:Serious Bug Reproducible:Always
 
Summary:
The LAContext localizedFallbackTitle is being ignored and only the "Cancel" button is being presented to the user.

Steps to Reproduce:
1) Run the KeychainTouchID Apple-provided sample application
2) Tap "Local Authentication" on the bottom tabbar
3) Tap "Touch ID authentication (custom)


Expected Results:
A second button saying "Enter PIN" should appear alongside the "Cancel" button

Actual Results:
Just the Cancel button appears

Version:
iOS 8.3 / 12F70

Notes:
This is very serious, as it effectively prevents users from my app which elected to use TouchID to access their data if they somehow can't use their registered finger tips. The fallback button serves exactly to allow them to enter a pin or other password in these situations.

Configuration:
iPhone 5s

Comments

Jorge | 04-May-2015 07:48 PM

Thanks for the information. It is my opinion that this is a much worse UX, due to the following reasons:

1) If the user can't use the enrolled finger for any reason (a simple band-aid, for instance), she will likely never try another one she knows is not enrolled and potentially be blocked from using the TouchID-protected part of the app. This has actually happened in the field with users of my app.

2) If the user can't use any finger at all (she is using touch-screen compatible glove, for instance), she will be forced to remove the glove or, if the situation is more complicated than simply removing a glove, she will be blocked, without recourse.

3) In all cases, there's absolutely no visual indication describing this behavior, making users confused and unable to proceed by themselves.

Thanks for considering the above.

Apple Developer Relations | 04-May-2015 06:39 PM

This issue behaves as intended based on the following:

The additional button is shown after first failed match now.

Please update your bug report to let us know if this is still an issue for you.


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!