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

Sync error when updating a relationship from another device #538

Open
jphribovsek opened this issue Jan 26, 2016 · 4 comments
Open

Sync error when updating a relationship from another device #538

jphribovsek opened this issue Jan 26, 2016 · 4 comments

Comments

@jphribovsek
Copy link

2 entities: Entity1 and Entity2
Entity1 has a 1 to many relationships to Entity2
If an object A of type Entity2 points to an object B of type Entity1, then we make A points to another objectC of type Entity1 in a single operation (without nullifying in between), then an error is logged on other devices

            SPLogError(@"Simperium error: member %@ from diff wasn't in change", key);

Problem is the change being received is a diff of the simperium key string for that relationship

{
o = d;
v = "-32\t+18567dcee3074f78b24def6ffc039904";
}

but SPMemberEntity expects the value to be the Simperium key itself, not a diff

I assume a workaround is to modify the schema to force a replace of those values instead of a diff, the same way we do with Transformables. However, you might still want to consider this a bug

@danieljimenez
Copy link
Contributor

Bump, any update on this guys?

@jleandroperez
Copy link
Contributor

Sorry @danieljimenez, low priority (for now). Please, consider enabling the Replace schema option, as outlined by JP, at least for now. Other than that, patches are always welcome.

Thank you, hope you're doing great!

@danieljimenez
Copy link
Contributor

We just wanted to make sure that was the right approach, thanks!

@jleandroperez
Copy link
Contributor

I'm afraid that, for now, yes sir, that would be the right approach. Thanks for checking (and apologies about missing this ticket!)

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

No branches or pull requests

3 participants