@fabdarice - select your project > Capabilities tab > set Keychain sharing to On

from keychainaccess.

@twiedow

It seems that with iOS 10 this problems always occurs. I just could reproduce the problem when opening the sample app for this project (using the master) and running it in the simulator (iPhone 7 / iPad with iOS 10).

Please add code signing entitlements to the app. I've just fixed at fb4529d for the example project. From iOS 10, entitlements file is always needed for writing Keychain even without sharing.

from keychainaccess.

Same issue here when I use accessGroup and run in real device.

• Xcode 8.1.
• iPhone 6 plus.
• Swift 2.3

I solved it by:
First I Turn on the Keychain Sharing capability.

Then adding "App ID prefix" AB123CDE45.example like this
let keychain = Keychain(service: "name", accessGroup: "AB123CDE45.example")

Source: http://evgenii.com/blog/sharing-keychain-in-ios/

from keychainaccess.

@kishikawakatsumi From the Xcode 8.2 beta release notes :

Resolved in Xcode 8.2 beta - IDE
Keychain APIs work correctly in Simulator. (28338972)

from keychainaccess.

I fixed the issue by writing an own library which is no-nonsense just-keychain interaction. I will open-source it next week.

from keychainaccess.

@kishikawakatsumi From the Xcode 8.1 GM release notes :

Known Issues - Simulator
Keychain APIs may fail to work in the Simulator if your entitlements file doesn’t contain a value for the application-identifier entitlement. (28338972)
Workaround: Add a user-defined build setting to your target named ENTITLEMENTS_REQUIRED and set the value to YES. This will cause Xcode to automatically insert an application-identifier entitlement when building.

from keychainaccess.

Anything that touches security APIs must be code signed properly or it will cause weird failures by design.
This includes things that call them indirectly.
Just code sign everything and use proper entitlements.

On 14 Sep 2016, at 22:54, kishikawa katsumi [email protected] wrote:

@twiedow

It seems that with iOS 10 this problems always occurs. I just could reproduce the problem when opening the sample app for this project (using the master) and running it in the simulator (iPhone 7 / iPad with iOS 10).

Please add code signing entitlements to the app. I've just fixed at fb4529d for the example project. From iOS 10, entitlements file is always needed for writing Keychain even without sharing.

―
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

from keychainaccess.

I was receiving this error I did as @lfaoro suggested and I am no longer seeing it.

from keychainaccess.

@petrdvorak that's a good point. I found in this thread that just having the entitlements is good enough (if you have at least one of the other capabilities). I just tested, created the entitlements for the Keychain Sharing, then turn it off and then turn on another capability like iCloud for example and still works! I know this is not ideal but I thought maybe is useful for somebody.

from keychainaccess.

For those having problems with Frameworks, the only way I was able to workaround this was by creating a host App. I added a new target, enabled Keychain Sharing in capabilities and then in the test target I selected the Host Application, no need to add the test files to that target:

from keychainaccess.

If somebody is getting here desperately trying to get it to work without enabling Keychain Sharing. Just omit the accessGroup parameter when creating the Keychain object.

Explicitly passing my bundle id, then creating the entitlements file and adding the code signing entitlements always turned on Keychain sharing automatically. Turning it off again results in Xcode wiping these settings resulting in a deadlocking cycle.

Update: this seems to only work on a device and not in the simulator.

Update #2:
According to this thread it seems to be an Xcode bug related to code signing.

from keychainaccess.

if anyone only crash with accessGroup, @forsan give the true answer!

or you can see directly: http://evgenii.com/blog/sharing-keychain-in-ios/

from keychainaccess.

Could you please show me your code that to get/set keychain items? I think some factors about the error, but I need more details to identify the cause.

from keychainaccess.

I have the same issue with a mac app (running in agent mode). Here are my codes

    let bundleIdentifier = NSBundle.mainBundle().bundleIdentifier
    self.keychain = Keychain(service: bundleIdentifier!)
    if let password = self.keychain!.getString("password") {
        println("Found password = \(password)")
    }
    else {
        println("No password found in keychain")
    }

the issue only appears sporadically. I found some related SO questions here

http://stackoverflow.com/questions/22082996/testing-the-keychain-osstatus-error-34018?lq=1
http://stackoverflow.com/questions/20344255/secitemadd-and-secitemcopymatching-returns-error-code-34018-errsecmissingentit/22305193#22305193

from keychainaccess.

I'm seeing this as well. It seems to happen only when updating the keychain item, not when initially creating it. The update succeeds, however.

Turning on the Keychain Sharing capability fixes the issue.

from keychainaccess.

Interesting. I noticed I never had the issue on a production (archived) build. Did you? Might try turning on KeyChain sharing, just to be sure.

from keychainaccess.

For security, and contrary to Apple's docs, don't update a keychain item, instead, remove it and create a replacement.

from keychainaccess.

I never had this issue until I update to Swift 2 and test on iOS 9 today, is there something changed in new version?

from keychainaccess.

@wangshengjia I experienced the same...after the Swift 2 update.

from keychainaccess.

Swift 2 or Xcode 7, not sure which causes the issue, but they both go together.
Update: actually I have only seen this on an iOS9 device so far.

from keychainaccess.

Same here. Swift2 + iOS9.

from keychainaccess.

I'm getting this issue with Swift 1.2 and iOS 8. Adding Keychain Sharing worked for fixed me too.

Is enabling Keychain Sharing the correct fix or a bit of a hack around the problem?

from keychainaccess.

I've just had this problem re-occue with Keychain Sharing enabled. @kishikawakatsumi any ideas on a Fix?

from keychainaccess.

This is becoming a really frustrating issue for us. I'm able to replicate quite consistently. When running our application after deleting it from the device, we run in to this issue when trying to access the keychain shortly after creating it. During the gap between creating the keychain and receiving this error on next access, the app is exited and re-entered.

@kishikawakatsumi I'm hoping you could advise me on a possible cause and/or fix shortly. I may have to consider finding another keychain wrapper/framework.

from keychainaccess.

...now able to replication without exiting the app.

from keychainaccess.

Done a fair bit of digging tonight. Looks like this is actually a bug in Security.framework:

https://forums.developer.apple.com/thread/4743

Last response from Apple was on Jul 27, 2015 1:22 AM. They still haven't confirmed on this thread that the bug has been resolved.

from keychainaccess.

This makes sense (that it's an apple bug). Keychain is a mess.

from keychainaccess.

This happens on Mac apps as well, Keychain Sharing fixes it but then you can't distribute the app outside the App Store if you use any of the features under Capabilities

from keychainaccess.

I keep experiencing this as well.
You guys are mentioning that turning on Sharing Capability fixes it.
To turn it on, are you just adding ".synchronizable(true)" to keychain?

from keychainaccess.

Same issue here as well. "Keychain Sharing" is enabled.

from keychainaccess.

Can anyone else confirm that turning on Keychain sharing works? It's still failing for me.

from keychainaccess.

What is the value for Keychain in your Info.plist?
My previous value of {AppID}.* did not work any longer after updating to SDK 9 Swift 2. I needed a fully qualified name like {AppID}.com.domain.app

from keychainaccess.

Same issue here :(
Swift2 + iOS9

from keychainaccess.

It seems like enabling keychain sharing solves this issue for me.

from keychainaccess.

Error is still occurring occasionally.
Swift 2.0 + iOS9

from keychainaccess.

I cannot reproduce such a problem. Can anyone share a reproducible project? Or could you please report this issue with your code snippets. "Same issue here" is nothing to help for me 🙇

from keychainaccess.

And @kylejm's mentioned it https://forums.developer.apple.com/thread/4743 . Is it help for this problem?

from keychainaccess.

It still happens for me. It happens intermittently when the keychain is accessed after some time has passed since hitting a breakpoint.

In that thread an Apple employee has recently commented saying that we should all file a radar each so that not only can we see the status of the bug being fixed, but it will also go up on Apple's priority. I'm going to do so tomorrow morning when I'm at my desk.

from keychainaccess.

You can't see the status of other bugs, even ones that you are a dupe of. That is one of the reasons why bugreporter is garbage.

from keychainaccess.

Just my 2c, I was having this issue in a Mac app and it went away when I ensured I never overwrite an existing value by using this little method:

extension Keychain {    
    func updateIfNeeded(key: String, value: String?) {
        if self[key] != value {
            self[key] = value
        }
    }
}

from keychainaccess.

Also seeing this issue in our iOS app. Adding Keychain Sharing didn't fix the issue and clearing storage using .removeAll() before updating also didn't work. Doing individual deleting then re-adding seems to be working, will update if I find out more information.

Update: Still getting the issue, including sometimes when I am reading from keychain. Can't work out any consistent repro steps.

from keychainaccess.

I'm also still having this issue. For me it works fine in the simulator but as soon as I run on a real device it begins failing. I have a super simple singleton class that manages an oauth token for me.

import KeychainAccess

class Settings {

  struct Key {
    static let webServiceAuthToken = "webServiceAuthToken"
  }

  class var shared : Settings {

    struct Static {
      static let instance = Settings()
    }

    return Static.instance
  }

  var webServiceBaseUrl: String {
    return NSBundle.mainBundle().infoDictionary!["webServiceBaseUrl"] as! String
  }

  var webServiceAuthToken: String? {
    get {
      let keychain = Keychain(service: webServiceBaseUrl)
      do {
        return try keychain.getString(Key.webServiceAuthToken)
      } catch let error {
        log.error("Error getting webServiceAuthToken from keychain: \(error)")
      }
      return nil
    }
    set(value) {
      let keychain = Keychain(service: webServiceBaseUrl)
      if value != nil {
        do {
          try keychain.remove(Key.webServiceAuthToken) // NB: This does seem to help
          try keychain.set(value!, key: Key.webServiceAuthToken)
        } catch let error {
          log.error("Error saving webServiceAuthToken to keychain: \(error)")
        }
      } else {
        do {
          try keychain.remove(Key.webServiceAuthToken)
        } catch let error {
          log.error("Error removing webServiceAuthToken from keychain: \(error)")
        }
      }
    }
  }

from keychainaccess.

Same here (KeychainAccess v2.3.3, iOS9.2)

from keychainaccess.

same error here! It doesn't happen on simulator but on device i can consistently reproduce it. has anyone been able to find a solution?

Turning keychain sharing didn't work. I also tried the suggestion to not overwrite an existing value if its same but that too didn't help.

Additionally: For me this error occurs only if iPhone is in debugging mode (attached to mac by cable)

Swift2, ios 9.1

OSStatus error:[-34018] Internal error when a required entitlement isn't present, client has neither application-identifier nor keychain-access-groups entitlements.
fatal error: 'try!' expression unexpectedly raised an error: Error Domain=com.kishikawakatsumi.KeychainAccess.error Code=-34018 "Internal error when a required entitlement isn't present, client has neither application-identifier nor keychain-access-groups entitlements." UserInfo={NSLocalizedDescription=Internal error when a required entitlement isn't present, client has neither application-identifier nor keychain-access-groups entitlements.}:

from keychainaccess.

Where are you guys placing your keychain code? This error started happening to me when I was querying keychain in applicationDidFinishLaunchingWithOptions. There has been speculation that this is too early. I moved it to the viewDidLoad of my initial view controller and have not experienced the issue since then.

from keychainaccess.

As reported by @hborders matthewpalmer/Locksmith#31 it seems like an Apple bug.

In my case, I got the issue when running from Xcode on the device, but after killing the app and relaunching from the device the error had disappeared.

Looking back into https://forums.developer.apple.com/thread/4743, referenced by @kylejm, the last answer from eskimo suggests that the bug has been fixed in iOS 9.3.

from keychainaccess.

I am suffering under the same issue. I have an app which stores credentials to Keychain but is not distributed via Mac App Store which means that Keychain Sharing can not be activated.

Does anyone have a fix for that?

from keychainaccess.

@skreutzberger From my experience, this problem made keychain unusable for me on real (non-simulator) devices until iOS 9.3 came out.

from keychainaccess.

@jpaas so it is fixed in 9.3? I am developing for OS X and require 10.11. Seems it is not fixed there, yet :(

from keychainaccess.

@skreutzberger yes fixed in iOS 9.3. Sorry I can't speak to OS X. In fact I didn't even know it was problem on OS X too.

from keychainaccess.

I asked them at https://forums.developer.apple.com/thread/4743

from keychainaccess.

@jpaas I normally added Keychain support via Capabilities Tab but then I needed to activate Sharing to make it work -> which lead to issues with Mac App Store.

Do you know how I can manually add the minimum necessary entitlements without cloud sharing to Info.plist?

from keychainaccess.

@skreutzberger I had the same problem. I could only get it to work by enabling cloud sharing.

from keychainaccess.

I maybe missing something obvious, but do you guys have an *.entitlements file that defines your Keychain Access Group[s]?

from keychainaccess.

Sorry I mis-spoke. I just looked back at my entitlements, and it seems I was able to get it to work without keychain sharing. I must have turned it off at some point.

from keychainaccess.

Can you share the content of your entitlements file (maybe with fake values)? I constantly get signing errors on mine. Are you using it for an App Store app?

from keychainaccess.

Here is what I have in my entitlements (This is Enterprise and Dev, not App Store, so YMMV)

The first value we use when we share between apps. The 2nd is for app specific keychain storage.

The first value is the prefix + a random value we use (company name)

from keychainaccess.

Hmm, looks like mine.

Are you using "Developer ID *" as signing identity?

from keychainaccess.

@skreutzberger - yes but without the *. i've randomly gotten the issue (once in a blue moon)

I've noticed in an SDK I use (for another project) that kicks off some keychain access in an initialize method, that if it is invoked in the didFinishLaunchingWithOptions application delegate it would fail virtually every time.

from keychainaccess.

Good luck but isn't this project right here a no-nonsense, just keychain interaction? The problem is in Keychain

from keychainaccess.

This comment helped to solve the problem on macOS

from keychainaccess.

Anyone knows a workaround for Unit Tests? I'm facing this problem in Xcode 8 GM. I have tried to add this to my test target with no luck:

codesign --verify --force --sign "$CODE_SIGN_IDENTITY" "$CODESIGNING_FOLDER_PATH"

By the way my project is a Framework so I don't have the capabilities tab.

from keychainaccess.

Any news for this?
It seems that with iOS 10 this problems always occurs. I just could reproduce the problem when opening the sample app for this project (using the master) and running it in the simulator (iPhone 7 / iPad with iOS 10).

Btw, the sample project has a bug when opening the input view controller. Xcode 8 messes with the connections of the IBActions. The app crashes with an error saying that there is no selector of name ... I fixed by changing by changing the method signature and re-connect the actions in the interface builder.

from keychainaccess.

@twiedow Also the example project has been fixed already in swift-3.0 branch 😉 Thanks!

from keychainaccess.

@tolkiana I've the same problem... I'm working on a framework with Keychain support, so there is no capabilities Tab... Did u find a solution already?

from keychainaccess.

@hons82 not exactly, my solution was making my tests with mock objects, similar way you would do it with NSUserDefaults.

from keychainaccess.

I was receiving this error in iOS 10 I did as @lfaoro suggested and I am no longer seeing it.

from keychainaccess.

I'm struggling to find a sulotion to this when using Keychain in Unit tests. Anyone have any tips?

from keychainaccess.

Guys, a little tiny note - are you sure you want to have "Keychain Sharing" feature on? For my project (related to security element of mobile banking) this is strongly undesired...

from keychainaccess.

This error also occurs in a project I am currently working on.

Error

OSStatus error:[-34018] Internal error when a required entitlement isn't present, client has neither application-identifier nor keychain-access-groups entitlements.

NOTE: The error appears on Xcode console. The app does not crash.

Facts

1. Xcode version is 8.0 (8A218a).
2. Our project uses Swift version 2.3.
3. Our project uses the version 2.4.0 of this library (https://github.com/kishikawakatsumi/KeychainAccess)
4. The error occurs while running the app in an iOS 10 simulator instance.
5. The error does not occur while running the app in an iOS 9.3 simulator instance.
6. The error occurs either the Keychain instance is created without any arguments or setting just the "storeService" parameter.
7. The error does not occur if the keychain-access-group entitlement is set for the target.
8. The error occurs if the entitlements file is set but empty.
9. The error DOES NOT OCCUR while running the app on an iPhone with iOS 10!!!

Hypothesis

iOS 10 simulator or Xcode bug. 😞 (Even maybe a regression bug...)

Related

• https://forums.developer.apple.com/thread/62847 points to the bug hypothesis.

from keychainaccess.

if you use .synchronizable(true) try turning iCloud in Capabilities tab and selecting Services: CloudKit

For me, everything worked fine on simulator. If keychain-access-group entitlement is configured, everything works, remove it and it fails. That until I put it on a device.
After debugging it for hours, reading Apple's thread on devforums I arrived at a conclusion, that iCloud enabling the keychain with .synchronizable(true) is ignored in simulator, but not on device.
After turning iCloud in Capabilities tab and selecting Services: CloudKit, it started working. Turned it off and it still works. It appears that turning it on, allowed the keychain to be reset somehow.

Repeated the same on two different iOS10 devices with the same result -> initial crash with -34018 error. Turning iCloud entitlement on and it goes away, after which iCloud can be turned off.

from keychainaccess.

Here's my experience with it :

• Background : Xcode 8, iOS 10 simulator, iPhone iOS 9.3.3, iPhone iOS 8, free developer certificate (6days limit)
• keychain sharing : on
• simple code : (on button click)

        let keychain = Keychain(service: "somewhere")
        keychain["kishikawakatsumi"] = "works"
        let token = keychain["kishikawakatsumi"]
        print(token)
        label.text=token

Result :

• iOS simulator : works
• iPhone iOS 8 : works
• iPhone iOS 9.3.3 : works only when running from xcode, not working if the same app is running from device

Is it because of the free developer certificate in iOS 9 that cannot open key chain ? If so why it can work when running from Xcode

Maybe it can help somehow

from keychainaccess.

@thebluepotato Although "Xcode 8.1 Release Notes" say exactly the same, I could not make it work yet using Xcode Version 8.1 (8B62)...

from keychainaccess.

@tolkiana thanks a lot. I did both mocking for unit tests and sample app for graphical testing.

I'm using an enterprise profile, and I didn't need an entitlements file for devices running iOS 9 and 10. The only place I need that file is when I run it on simulator. There I need to switch on keychain sharing

from keychainaccess.

@thebluepotato have you tried this yet on Xcode 8.2 beta and confirmed that the issue has been resolved?

from keychainaccess.

I encounter same issue yesterday. Probably, it is a simulator bug on XCode8.1.

On my Xcode, when using iOS 10 Device Simualtors(iPhoneSE / iPhone7), this error always shows on console, but does NOT show any errors on using iOS9.x one.

Here's my code. this works fine with iOS9.x Simualtors, iPhone6s(iOS9.3), iPad Pro(iOS10.1)

    let keychain = Keychain(service: "MY SERVICE ID")
    keychain["auth_token"] = token

My Background as below. license type may not affect on this error.

• XCode8.1/ Swift3
• Keychain sharing OFF
• install this library via carthage.
• Deployment target 9.0
• Apple Developer Program / Entity Type:Company / Organization

from keychainaccess.

I have enabled keychain sharing. but problem is some times keychain works. and some times can't fetch from from keychain and throws error: "Internal error when a required entitlement isn't present, client has neither application-identifier nor keychain-access-groups entitlements."

does anyone have any idea?

from keychainaccess.

I have already tried and it worked on Xcode 8.2 (8C38)❗️

from keychainaccess.

I figured it out. my keychain was corrupted. I think because my device is jailbroken

from keychainaccess.

I believe it was fixed by Xcode 8.2

from keychainaccess.

probably spent 10 more minutes on this than necessary
http://evgenii.com/blog/sharing-keychain-in-ios/

Keychain(service: "com.8secondz.ios.token", accessGroup: "AB123DE123.8secondz")
this solved the day.

perhaps it would be clearer with a helper to spoon feed clarity
Keychain(service: "com.8secondz.ios.token", appIdentifier: "48K8QNQU37", groupIdentifier:"8secondz")

from keychainaccess.

Interface of Xcode is a little bit changed in version 11.6. It looks like this. In my case, I use keychain in my watch. I need to add capability of Keychain sharing to watchkit extension and add a group name and fill it into aceessGroup: "Your-App-ID.Your-Group-Name"

from keychainaccess.