Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors when trying to identify user on iOS #191

Closed
SYoder1 opened this issue Aug 29, 2023 · 3 comments · Fixed by customerio/customerio-ios#376
Closed

Errors when trying to identify user on iOS #191

SYoder1 opened this issue Aug 29, 2023 · 3 comments · Fixed by customerio/customerio-ios#376

Comments

@SYoder1
Copy link

SYoder1 commented Aug 29, 2023

SDK version: 3.1.8

Are logs available? Yes

Describe the issue
I am trying to setup the customer io sdk for the first time, and was able to get Android working, but on iOS when ever I call CustomerIO.identify(userId); the device token never shows up under the user devices. When I look into the logs I see the errors above.

Screenshots
Screenshot 2023-08-29 at 4 06 31 PM

Additional context

@Shahroz16
Copy link
Contributor

Hey @SYoder1, thank you for reaching out. Can you please give me details, how does the SDK initialization looks like?

@SYoder1
Copy link
Author

SYoder1 commented Aug 30, 2023

Hey @Shahroz16! I actually delete the whole SDK (JS and native code) and re-added it followed the SDK installation guide to the letter. And after that it still didn't work, and I was seeing the same error.

After doing a lot more playing around, the ID I am using is from auth0, so the ID look something like social-login|1234567890abcde. If I remove the pipe | from the IDs the token get registered and uploaded and can be seen in the device tab of the user, but if I put the pipe back in, it will not upload. It looks like I can pass the email as the first parameter in the identify() and it will match things up correctly, but not all of our users have a email registered. Do you have any ideas?

@Shahroz16
Copy link
Contributor

Hey @SYoder1, we have managed to replicate the issue and will be rolling out a fix soon. Thank you for your patience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants