Phone app data different?

[EricBWS]

Possible bug.

I updated a table and added several columns.  After my work I changed the major revision number and saved the app and then synced the app in the editor. The editor was showing correct info but no matter how many times I synced my phone it would not show updated data, the version in "About" was the correctly updated version. I finally logged out and back in to get it to update.

Now I still have different data showing on my phone vs the computer, I have a format rule that shouldn't apply, on the editor it is correct, on my phone it is applying the rule.

@WillowMobileSys ever seen anything like this?

[WillowMobileSys]

---

@EricBWS wrote:

no matter how many times I synced my phone it would not show updated data, the version in "About" was the correctly updated version. I finally logged out and back in to get it to update.

---

Yes, I have seen similar issues with app updates in an Enterprise account where we manage by Stable/Latest versions.  It's a little fuzzy now but I believe we had issues where a new feature was implemented and at least one user on Latest did not see that update right away upon a Sync - in spite of the version reflecting correctly.  It seemed it took some time for the actual app definition change to flow through to the device.  This might be expected and the bug might be that the version number is updated before the app definition is fully pushed.

We have also had cases of users on Stabile versions not getting the updates and needing to log out and back in to "refresh" things.  Though these seemed to be more of a device side issue where the users couldn't access the app properly in the first place. Maybe related??

Then there is the nightmare of adding new columns and trying to get that pushed out to users and avoid column mis-match errors!!   It is simply impossible to come up with a viable approach to get these changes rolled out to users seamlessly without errors occurring.  The more frequent changes are pushed the more lilley errors will occur.  It greatly affects how app changes are managed resulting in the old approach of bundling lots of changes together and performing periodic controlled roll-outs...only to still encounter errors!!!  Simply unacceptable!!!  The thing is, there is a way for AppSheet to help with this there just isn't any focus on it.