Simperium found local object that doesn't exist remotely yet

[lukegeiger]

@jleandroperez sorry to be a pest, but I am seeing this now, in my logs and this entity is not being saved to simperium but it is saving locally. I can get this to replicate 10/10...

The object that I am trying to save is called a Lineup... It is apart of a one to many relationship with a Team Object. A team has many lineups...

The Lineup object has another one to many relationship with something called LineupStats. The Lineup stats object does not save to Simperium either.

Also it should be worth noting that the Lineup object has a transformable data that I am using as an array to store an array of strings.

Let me know what information you need.

[lukegeiger]

@jleandroperez any word on this one? I need to push out a version and don't want to submit to app store if I don't have an entity syncing.

[jleandroperez]

Hello there Luke,

On the contrary, it's our goal to keep the library bug free. We really appreciate that you take the time to report any weirdness you experience (thanks!!).

As far as i understand, the Lineup entity is the one that fails to sync, is that correct?.

Data Model:
Team (1..)-> _Lineup* (1..)-> _LineupStats*

This error basically means that the entity has never been sync'ed. Would it be possible to get the logs for this glitch, on a fresh account? (by this i mean, can we get the logs printed out when the library attempts to upload the broken entity?).

Thank you Luke!

[lukegeiger]

@jleandroperez no problem I realize my data model and app architecture is a bit more complex than most, and it probably finds a lot of the edge cases for some things. Yes the Lineup is is the one that fails sync. I will email you the logs.

In the meantime, for what its worth, I downgraded Simperium back to v 0.6.9 and that seems to be the most recent version that 100% supports my apps data model and structure, with no errors.

[prvnl]

I must agree on the downgrade to v0.6.9. I did the same for my apps a few days ago..

[jleandroperez]

Sorry to hear you're having issues gentleman. Please, beware that 0.6.9 had a couple big bad bugs that fixed in 0.7.0 (#359 #356).

Plus, we encountered a deadlock in Core Data (Fixed with an architecture change in #376, 0.7.2).

@prvnl may i ask you if you're also experiencing this issue? (Is this the blocker for you to upgrade to the latest?).

@lukegeiger I've been trying to reproduce this glitch, with no luck. Would it be possible to take a look running directly your app?.

Thanks in advance!

[prvnl]

Hi @jleandroperez,

I'm not sure if it's the same issue. But since upgrading to one of the latest versions 0.7.1 and 0.7.2, the users of my apps are complaining of loosing data. So they enter information, but the next day the data is gone. This is not an isolated issue and happens to many users, but I'm not able to replicate this issue.

Edit: This does not happen when the Simperium Sync is disabled.

Loosing data is the worst thing that can happen to the users of my apps, so I had to make the decision to downgrade to a more stable version.

Regards Patrick

[jleandroperez]

@prvnl would definitely love to get that fixed, as soon as possible. If you manage to get repro steps, or anything that might shed some light (which would be just awesome!), by all means, please, say the word.

In the meantime, this issue plus #395 are definitely the best candidates. We'll track this down, thanks for the report Patrick!.

[lukegeiger]

@jleandroperez yes of course. you are on the repo, and I have created a branch for you called SimpError. Pull from that. It takes some time to reproduce especially if you are not familiar with the app so I apologize! Below are the steps...

1. I have created an account for you with some populated data your username is jorgesimp@6thmanapps.com the password is simperium

2)Tap the new game button, select a league, two teams, and five players from each team to start a game. Upon starting a game I sometimes get some error codes so take a look in the debugger if you see some.

3. Input at least one stat in the game by tapping on a player, tapping on an area of the court, and follow the flow that appears.

4)After one stat is entered you can now finish the game.. Adjust the time in the game to 0:00 and end the first half... The second half will start, and as soon as it does you can adjust the time back to 0:00

5. End the game.

6)There is where logs are suspect to appear.

7. At this point in time, all data appears correct in the app, but if you then proceed to tap on the Leagues button on the home screen (The screen where you can tap New Game, Leagues, or account), then tap on a team, the team profile screen will appear. Near the end of the side nav there is a row that says Lineups tap that. As you can see, if you have played on game you should see lineup objects populate the table.

8. Once you can confirm you see lineups there, delete the app/signout and log back in, tap on the same team and tap on the lineups row, and the lineups will be gone. Again this only happens in version after 0.6.9

If you want to test Simperium Error [Client Error : 404] while processing changes for object This log appears everytime if you start a game, and tap the end game button which proceeds to delete the game....

Let me know if you need more help.

[jleandroperez]

@lukegeiger thank you for setting up the sample account!!.

Will get back to you as soon as possible, thanks!

[jleandroperez]

@lukegeiger hello there,

I did manage to reproduce the error Simperium found local object that doesn't exist remotely yet (thank you very much for your help!).

It should be fixed in Develop, would it be possible to confirm?.

(#402 is still pending).

Again, thank you!

[lukegeiger]

@jleandroperez sorry for late response. This seems to be working on my end.

[jleandroperez]

@lukegeiger awesome!. I'll be working on #402.

I'll make sure to /cc you as soon as Mark 0.7.5 is released.

Thanks again Luke!

[prvnl]

Hi @jleandroperez!

I've finally managed to reproduce the issue my apps where having (#387 & #395 & this issue), they are all fixed in the current develop version! Thanks for all the hard work and also to @lukegeiger for his effort in getting this fixed!

Regards,

Patrick

[jleandroperez]

@prvnl thanks for testing the latest develop!.

++ many thanks to @lukegeiger for reporting this bug.

We'll be tagging a new version shortly, with the fixes in.