I’ve submitted claims to firstname.lastname@example.org as well about this same issue, and they keep telling me that its due to the memory on the device.
Inputting something into the app via a form always works the first time after the app “clears the cache.” But upon further form inputs, there seems to be a point where the app starts to slow down, and you know that you’re bound to have a resync or “kick-out” as you describe that clears the data on the form you’ve just tried to input.
My theory is that the Appsheet app stores the effects of the data change directly onto your own device. Even if the app saves your data onto the sheet in the backend successfully, the cached data remains. As you continue to submit further changes, the cached data overwhelms your allotted local storage for the Appsheet app.
Some things that can predispose to this problem
- Large tables
- Ref values connecting different tables
That’s just my theory, but I’ve had this problem for a while now as well.