Solved

errSameIDs or errAnonDistinctIdNonGUIDForm error

  • 27 August 2020
  • 5 replies
  • 438 views
A
Badge

If I use my email to identify I get the errSameIDs error and when I use my subject from my JWT I get the errAnonDistinctIdNonGUIDForm error.

Do I really need to add UUID’s to my data for this to work?

icon

Best answer by Arte 16 October 2020, 10:54

Hi @Arte! You are not alone I have been searching for it and I recently found your post. 

Hey, so I found it it was caused by my user being undefined the first time I called identify, I hope this helps you!

View original

5 replies

A
Badge

Also it’s quite strange that when I search for these errors I’m literally the only one who ever had this? :sweat_smile:

A

Hi @Arte! You are not alone I have been searching for it and I recently found your post. 

A
Badge

Hi @Arte! You are not alone I have been searching for it and I recently found your post. 

Hey, so I found it it was caused by my user being undefined the first time I called identify, I hope this helps you!

A

Hi @Arte! You are not alone I have been searching for it and I recently found your post. 

Hey, so I found it it was caused by my user being undefined the first time I called identify, I hope this helps you!

Hi @Arte ! Thanks for the prompt response. Do you mind giving an example of your own testing environment please? I am helping someone to implement it and I wanted to see if we might have the same issue.

S

You are not the first one. I just came across the same error (not really a breaking error, but it shows as a property on my Identify event) and saw your page. My situation is that, our app is already built out, so there is no sign up, so I don’t have a chance to “alias”; I directly have to use “identify”. What you (Arte) say makes sense. I am also using “people.set_once()” to set up some one time property on the user profile, that I’d ideally would have done on sign up.

Reply


Mixpanel