SecItemAdd returns errSecAuthFailed

Hello,

I'm experiencing a weird issue on the iOS 15 simulator (unfortunately I don't have a device with 15 installed yet).

The issue I see is that the call to SecItemAdd returns OSStatus -25293 (errSecAuthFailed).

The attributes dictionary passed looks like this:

var query: [String : Any] = [
			kSecClass as String: kSecClassGenericPassword,
			kSecAttrAccount as String: key,
			kSecAttrService as String: service,
			kSecAttrAccessControl as String: getSecAccessControl(),
			kSecUseAuthenticationContext as String: context,
			kSecValueData as String: data
        ]

the getSecAccessControl returns a SecAccessControl created like this:

        access = SecAccessControlCreateWithFlags(nil,
			  kSecAttrAccessibleWhenUnlockedThisDeviceOnly,
			  .userPresence,
			  &error)

if I do not add the kSecAttrAccessControl item I don't see any error.

The same code works as expected on the simulator with iOS 14. Looking at the documentation didn't help, anybody has hints about this? Maybe it's bug I'm not aware of?

Thank you in advance

Post not yet marked as solved Up vote post of AlessioP Down vote post of AlessioP
7.5k views
Posted by
AlessioP
Reply

  • Same issue here. It's a relief to read I'm not the only person having this exact issue.

    —
    PuzzleMaster
Add a Comment

Replies

if I do not add the kSecAttrAccessControl item I don't see any error. Looking at the documentation didn't help, anybody has hints about this? Maybe it's bug I'm not aware of?

If removing kSecAttrAccessControl from the attributes dictionary results in this functionality working correctly then I would absolutely get a bug down for this. As a side note, I seen a related issue recently when adding access control attributes to a Keychain API for item creation, so this will need to get investigated during the beta cycle to see if there is a potential issue here.

Create a bug report here, and please respond back with the Feedback ID. Also, if you have time, please record the output of what is being stored in your attribute dictionary before SecItemAdd is called with lldb. Take this information and compare it against the local variables on your breakpoint and if your access control items print "(no summary)" then please make sure to add both the local variables and lldb info to the bug report.

Matt Eaton
DTS Engineering, CoreOS
meaton3@apple.com
Posted by
meaton
Up vote reply of meaton Down vote reply of meaton
Add a Comment

Hello Matt, thanks for your reply.

I've submitted a bug report, FeedBack ID: FB9414546

Posted by
AlessioP
Up vote reply of AlessioP Down vote reply of AlessioP
Add a Comment

I've submitted a bug report, FeedBack ID: FB9414546

Thank you for submitting a bug report here. I see it internally.

Matt Eaton
DTS Engineering, CoreOS
meaton3@apple.com
Posted by
meaton
Up vote reply of meaton Down vote reply of meaton

  • I was seeing a different error initially as reported here: https://developer.apple.com/forums/thread/691213

    When I removed kSecAttrAccessible as String: kSecAttrAccessibleAfterFirstUnlock I then was able to confirm this behaviour is also occurs in iOS 15 simulator with Xcode 13.

    —
    craigaps
Add a Comment

Hello,

Same issue for me on ios 15 simultor. Any new elements in the bug report ?

Posted by
alexis123456789
Up vote reply of alexis123456789 Down vote reply of alexis123456789

  • Ditto. Code that works fine on iOS 12, 13, 14 and 15 (devices) fails on iOS 15 simulator. SecItemAdd returning errSecAuthFailed. kSecAttrAccessControl object has kSecAccessControlBiometryCurrentSet|kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly

    —
    michaelr
Add a Comment

Ditto. Code that works fine on iOS 12, 13, 14 and 15 (devices) fails on iOS 15 simulator.

SecItemAdd returning errSecAuthFailed. kSecAttrAccessControl object has kSecAccessControlBiometryCurrentSet|kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly

Posted by
michaelr
Up vote reply of michaelr Down vote reply of michaelr
Add a Comment

I am also seeing this issue on the iOS 15 simulator. I can't view the bug report on the Feedback ID link posted above. What is the status?

Posted by
dcolemanartium
Up vote reply of dcolemanartium Down vote reply of dcolemanartium

  • Recent Similar Reports: None

    Resolution: Open

    —
    AlessioP
Add a Comment

Hi Matt Do you have any updates on this? It's a real show stopper for us if you could please provide some guidance. Thanks

Posted by
craigaps
Up vote reply of craigaps Down vote reply of craigaps
Add a Comment

There have been several reports here of testing this on the iOS simulator. While the simulator works well is most cases, it's not an exact representation of what with happen on a physical iOS device, especially with Biometric Authentication. So the first step is that I would always test this on a physical device when possible.

Next, regarding:

SecItemAdd returning errSecAuthFailed. kSecAttrAccessControl object has kSecAccessControlBiometryCurrentSet|kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly

This is a known issue right now and is being tracked against (r. 82890873). There is no update on when this will make it to a release, so the only thing that I can advise at this point is to create a bug report if you have not already and then please keep testing the iOS beta's as they are rolled out.

Matt Eaton
DTS Engineering, CoreOS
meaton3@apple.com
Posted by
meaton
Up vote reply of meaton Down vote reply of meaton
Add a Comment

I have the same problem on iOS simulator. XCode 13, iOS 15, MacOS Monterey, Mac with M1 processor.

Any updates?

Posted by
smajekp
Up vote reply of smajekp Down vote reply of smajekp
Add a Comment

Tested with Xcode 13.2 beta (13C5066c), iOS 15.2 simulator and still fails with same error. I'm on macOS Big Sur 11.6.1 (Intel).

Posted by
ImranRaheem
Up vote reply of ImranRaheem Down vote reply of ImranRaheem
Add a Comment

Looks like it is happening even with the coding examples from Apple: https://developer.apple.com/documentation/localauthentication/accessing_keychain_items_with_face_id_or_touch_id

Did someone check it is happening when testing on the latest iPhone 13 devices with iOS 15 building from Xcode 13?

Posted by
xcodefriend
Up vote reply of xcodefriend Down vote reply of xcodefriend

  • I haven't tested myself but from other reports I've seen, it seems to be a problem with simulator only

    —
    ImranRaheem
Add a Comment

I just checked on iPhone 13 Pro with iOS 15.0, and I can confirm that the error does not exist. On the simulator, we still experience the issue.

Posted by
vojche kushevski
Post not yet marked as solved Up vote reply of vojche kushevski Down vote reply of vojche kushevski
Add a Comment

We're experiencing this issue as well, opened a bug report: FB9777739.

Posted by
rfurman
Up vote reply of rfurman Down vote reply of rfurman
Add a Comment

Any updates?

Posted by
smajekp
Up vote reply of smajekp Down vote reply of smajekp
Add a Comment

Haven't heard anything from Apple support since filing a bug report.

Posted by
craigaps
Up vote reply of craigaps Down vote reply of craigaps
Add a Comment