-
-
Notifications
You must be signed in to change notification settings - Fork 52
iOS 10 needs keychain entitlements #48
Comments
this might only be for the simulator... |
Hi @dbankier was planning on updating. You'll need this for both Simulator and deploy. |
Thanks. Not sure why, but I only seemed to need it for the simulator. Was getting an entitlement conflict on an adhoc deploy to device... Probably my issue. |
@benbahrenburg @dbankier shouldn't need a custom Entitlements.plist. Should be able to place keys in tiapp.xml |
I've added the entitlements, but still get with iOS 10, securely V.2.2.0:
Or this another issue? |
Hi @markruys , Also make sure you clean your project. You might also want to check your team-id. This could have an impact. There is some good information on how to add and work with entitlements here https://www.appcelerator.com/blog/2016/09/ga-release-for-titanium-sdk-5-5-0-appcelerator-cli-5-5-0-appcelerator-studio-4-7-1/ |
I'm seeing this behavior also. Not completely clear on what it is I'm supposed to do. |
I added a appname.plist file to app/platform/ios/appname.plist that looks like this per the comment above: ` com.apple.keystore.access-keychain-keys com.apple.keystore.device `Still getting this error: Does anybody know what I'm missing here? I'm a bit lost as to where I'm jumping the tracks here. Using SDK 5.5.1. |
Also tried creating a file in app/platform/ios/entitlements.plist with those same values and see the same error also. Lost here. |
@joshualambert this worked for me.
Another trick is you can go into the SDK folder and enable keychain support. But would recommend trying the above before doing that. |
@benbahrenburg, adding the myApp.entitlements file with a keychain-access-groups to the Alloy iOS platform directory fixed the "Unable to set value to keychain" error for me. Thanks! |
I had previously added the myApp.entitlements file and all was well (I uploaded a build in December). But now I've started to get code signing entitlement errors when uploading. The errors relate to com.apple.keystore.device and com.apple.keystore.access-keychain-keys. Any ideas? |
With the latest version of Ti, I've found you don't need the entitlements. You might also want to double check your Xcode template |
I'm having the same problems, with the latest version: SDK 6.0.1, XCOde 8.2.1, iOS simulator I tried the myApp.entitlements solution without success. Any idea? |
Same problem here, anyone has any idea on how to fix it for the sim? |
I have tried creating the myappid.entitlements file and placing the xml keys directly in tiapp.xml. I am still getting the error [ERROR] : Unable to set value to keychain Error Domain=com.samsoffes.sskeychain Code=-34018 "errSecDefault" UserInfo={NSLocalizedDescription=errSecDefault} |
@agersoncgps would recommend double checking you are running the latest version of Xcode (8.3), Ti SDK (6.0.2) and Securely. I am running this combination in production without the need for an entitlements or modification to tiapp.xml file. The only non standard configuration I use is setting the min iOS target to 9. If in your configuration you are running into this error in the simulator, I would recommend writing a proxy that uses a plist save strategy when in the simulator and a keychain strategy when on device. |
Not sure where you want to update the README.md, but for iOS10 you need to have a custom
Entitlements.plist
file in your project with the following content:The text was updated successfully, but these errors were encountered: