If we add a new entry and leave the form open for some time without saving, the data we entered sometimes get lost and the form resets to empty.
This problem has been mentioned multiple times in this community. For example, in this thread from @RSHARM01 (which also contains a video demonstrating the issue):
Unfortunately, that topic has not received any official answers or solutions so far.
It my be related to the Automatic updates and the Quick sync.
This may be a function of the device. Apparently, Android apps will close and restart behind the scenes as the device user switches between apps and as other apps demand more resources. If the user switches from the AppSheet app to another, conditions may occur that prompt the OS to close the AppSheet app and reopen it when the user switches back to it.
This happens on Android, iPhone and Windows Chrome Browser.
@lizlynch I would appreciate it if you could bring my opening post to the attention of the engineers.
@Fabian_Weller - I’ve opened an internal ticket to track this issue. Apologies for the inconvenience.
We have seen support issues around this a few times but have so far been unable to reproduce or understand it. Use of “Quick Sync” seems to be a common factor, but forcing Quick Sync updates isn’t sufficient to observe the behavior. Personally I suspect it is related to some edge case behavior with Quick Sync, and I would suggest to disable that if you’re having this problem. I’d also be interested to hear back from anyone who tries that and finds it resolves or doesn’t resolve the issue.
This may be a function of the device. Apparently, Android apps will close and restart behind the scenes as the device user switches between apps and as other apps demand more resources. If the user switches from the AppSheet app to another, conditions may occur that prompt the OS to close the AppSheet app and reopen it when the user switches back to it.
This is definitely an issue. We try to account for it by storing form-in-progress state in a way that should normally persist through a forced restart. If the app does get restarted this way and the form recovery mechanism fails, it could present as the form getting reset, but would probably be accompanied by the app briefly showing some indication of startup - a blank screen, sync screen, loading spinner, etc. In the screen recording shared in the thread linked above, the form appears to just abruptly re-render in a reset state without any indication of the app restarting. So I believe that is evidence of a different issue.
Yes I think that is the case. But this happens also in very simple Apps, so to me it does not seem like an edge case.
Sadly we also cannot reproduce it or can tell when it usually happens.
@Fabian_Weller when you’ve seen this happening, was the app using the “Desktop design” or “new mobile framework”? Also have you noticed if it’s happening only in Add forms, or Edit forms, or both? Or any other notable details, like forms based on slices rather than tables?
Hi @Adam-google We don’t use the new desktop nor the new mobile framework. I think it started with the quick sync. It definitely happens on Adds with no slice. I’m pretty sure that it does not happen on edit.
Thanks, I did some more experimentation and was able to find a repro. Looking into a fix now.
You are awesome @Adam-google
