-
Notifications
You must be signed in to change notification settings - Fork 9
Cannot log in users on iOS simulator #31
Comments
@tejasranade Putting on your radar since this is pretty critical to the Identity Connect on-boarding process |
@toddanglin looking at it now. |
@toddanglin @tjvantoll For some reason, the keychain access API on simulator expects this file. I need to dig further why that's the case; and if we can insert it ourselves during the SDK install. Ideas welcome :) With the |
@tejasranade Thanks for the crazy quick response here! You’re absolutely right and I confirmed that adding that file fixes the issue. I’ll do some checking with the CLI team tomorrow about whether this can be automated with a hook like you suggest. I’ll reply back in here. |
Checked with @rosen-vladimirov. He reminded me that {N} plugins can totally just include a |
Awesome! We'll add that in. Anything to be mindful of, for apps that already have that file? |
That's great news. Looking at root cause, I wonder why the iOS Simulator requires this entitlement but actual iOS devices do not? I don't see much harm in just including the entitlement by default, but probably worth a root cause pass to see if it may impact other areas of the SDK... |
I don’t think there would be any repercussions of including an Out of curiosity, has this come up before with either the Appcelerator / Ionic / native iOS Kinvey SDKs? Just wondering if there’s any existing documentation and/or research we could use to get some background on what specifically is going on here. |
Hey guys, |
We found the root cause of this issue. It appears that the NativeScript cli adds an entitlements file, and corresponding entry in the Xcode build settings, by default during the iOS build process. This file is only added for the We tried overwriting this file in one of our samples, and we saw the issue go away. See KinveyApps/sample-Groceries#3 @rosen-vladimirov @tjvantoll this is something the CLI team should look into. We think the default entitlements file and the setting should not be necessary. Hat tip to @heyzooi for troubleshooting this issue! |
Hey @tejasranade. Just fyi we saw this and our CLI team will get back with you next week. (They’re heads down getting the {N} CLI ready for a 4.0 RC release right now.) |
Hey guys, |
Just ran into this myself on a project. Drove me crazy for the past couple hours debugging and trying to see why iOS wasn't signing in. I'll add the entitlements file for now but commenting to make sure I get updated with the 'final' word here 😄 PS - Loving Kinvey so far 🎉 |
@rosen-vladimirov makes sense, we'll add a default to the plugin. Stay tuned, that fix should be out soon. |
@toddanglin is putting together a template for NativeScript that uses Kinvey. As he was developing the template, and as I was testing it, we both hit a rather bizarre issue where a call to
Kinvey.User.login()
works on physical devices, but fails on iOS simulators (details below).Steps to Reproduce
Follow the steps to test Todd’s template here. To make testing easier you can use an app key of
"kid_HJUbdabvM"
, an app secret of"4a1ef9127ce24912a23f792b22831daf"
, a username of"foo"
, and a password of"foo"
.Run the app on an iOS simulator and attempt to log in using the credentials
"foo"
and"foo"
.Expected Result
The user logs in successfully and navigates to another page.
Actual Result
An error, and this in the console.
If you then run the exact same app with zero changes on a physical device the code log in should work exactly as expected—because reasons?
Version of Kinvey NativeScript SDK
3.9.10
Kinvey AppKey
(posted earlier)
NodeJS version
6.12.2
This is an odd one, and I wouldn’t believe this was happening if it hadn’t happened to both Todd and me. Hopefully this write up wasn’t too confusing, and if you need more details or help recreating this let me know.
The text was updated successfully, but these errors were encountered: