Does anyone else still see the error message "Sync Token Is Invalid"?

[WillowMobileSys]

I am curious if there are any others who have users that get the  "Sync Token Is Invalid" error message after an app push??

It would also be helpful to know if you use a database (which one), manage app changes with Latest/Stable versions and NEVER get the error message.

After several back and forths with AppSheet support claiming that the occurrence of the error msg "Sync Token Is Invalid" has been resolved,  our app received this message again today. 

What we know is that after making app changes and then pushing them out, there is typically 1 or 2 people who get this  "Sync Token Is Invalid" message.  To correct it we typically need the user to tap the "Reset Changes" option to clear the "stuck" edits and then Logout/Login to ensure app is updated.

To try to mitigate the issues, we do have a "force sync" function as part of the flow when a user accesses the app each day.  They are required to perform a "Punch In" activity and upon saving that the force sync is applied. 

But for some reason, a couple random users have issues that prevent the app from properly updating. 

Best we can tell, these issues occur only when we make database changes.  We use Big Query which is relatively new so could be part of the problem.  Users do sometimes have connection blips so that could be a culprit.

I do think if we could get the users in the habit of tapping that Sync button as their very first action each day, we would never see these issues.  That is easier suggested than done!

Please let me know if you have any helpful information regarding this problem.  I can pass it along to AppSheet in hopes it might help with their resolution efforts.

[Trevwiller]

Below are my understandings on this type of error when they come up. 

This can happen after changes to the tables if the data changes and are held in a latest version and the default is different, but the latest version is not visible to these users. 

The sync on start is not enabled to force a sync at startup causing the user to interact with a false version of the app. When updates come out this can be caused as the data retrieval just doesn't connect since it technically doesn't exist in the form it did when the edits were made. (The previous sync token)

The Table becomes so large that the table doesn't load fully for the app to correctly adjust the necessary row. Deeper data relations to the user needs to be made for security filtering. (If security filters are properly adjusted) Horizontal scaling can be effective for reducing rows to read reducing strain on the app.

If it is a branded app. Having users uninstall the app and reinstall can correct issues. 

Large amounts of edits at once. Since this is a time punch app just the sheer amount of users making a change at once can cause an error on random users.

The connection could be an issue as if their connection cuts out briefly the sync ticket is no longer valid for connecting them to the server

Sending out app notifications or emails to all users for upcoming updates could help with user understanding on actually syncing before entering data. (This should be an AppSheets update as it occurs often that the user just doesn't know an update came out and didn't sync before making changes. There needs to be something that does a forced sync for the users if an update was made to prevent issues. Shouldn't fall on the user or app designer to inform should just be automatic.)

Hope in some way this helps. I could also be off as there is no clear direction to why this error appears in the error log.

[WillowMobileSys]

Do you see this issue in any of your apps currently?

[Trevwiller]

Not at the moment, but this is the usual route we go through when it does. Has happened in the past several times. Most often it is on the user not syncing.

[WillowMobileSys]

---

@Trevwiller wrote:

Most often it is on the user not syncing.

---

Yes, except that older database app versions should continue to work as long as there were no changes to the pre-existing db columns - which is always the case for us.

Additionally, the error message is non-sense.  I have no idea what it refers to so I can't expect an end user would.   If there is truly an error, the message should indicate what the problem is.  The vibe I am getting from AppSheet is that the error should not be occurring - though they do not offer those kind of details.

You have seen the issues in the past?   Are your apps using a database?  Which one?   Do you use Latest/Stable versions to manage the app changes?

[Trevwiller]

Are you making changes to the DB? like adding new columns or changing column names?

also true. it just looks like gibberish. not sure what it references. 

If you make changes to structure or anything in a table/database you should either make the changes the new stable right after. Users that see the latest won't have to worry about this as the changes will already be delivered to them (after they sync) but if a stable exists before the changes. The users that are on default will encounter errors.

[Trevwiller]

Above is some that I have seen in the past, But there is one that appears with an error message below that looks like complete gibberish.

[イルカのえっちゃん]

---

@WillowMobileSys wrote:

I do think if we could get the users in the habit of tapping that Sync button as their very first action each day, we would never see these issues.  That is easier suggested than done!

---

This video might be helpful.
https://www.youtube.com/watch?v=bwNm5P4tks8