There is an app we are using in field. It’s been a while experiencing sync slowness issues and lot of users has unsynced data. When resolving the issue, we needed to change login credentials to the data source. This has lead to sync failures for most of the users. We are relying on show changes (i.e. users sending the changes to a dedicated email or checking the _recoveryData folder). However, there are some users (especially the ones whith a lot of unsynced data) who can’t show changes (i.e. if they try to click on this, nothing happens, the app takes them back to the home menu). Would anyone know why this is happening and how to deal with it so that no one loses the data? Also, would there be a way to access these data maybe from the device itself like app data or cache?
Please contact AppSheet Support for help with this.
Thanks Steve, I am doing that. For anyone who might be interested to take a look, let me know so that I can share a screen recording describing the issue.
Coming back here to share my frustration with Appsheet Support team.
So, I have contacted the team as @Steve suggested, the support agent asked me if I have tried the manual recovery which I confirmed (as I have already indicated it in the issue submission). I even shared a screen recording with him describing the issue we are facing (i.e. it’s a screen recording of a tablet facing this issue). After a long conversation with the support agent, he said that he is going to share this with the specialist and get back to me. After almost a week of waiting, this morning I received an answer asking me to do the very same thing I indicated that it’s not working from the beginning. Below is the escalation email together with the answer;
I expected the team to at least read the script of my conversation with the Support agent. So frustrating considering that we are on an enterprise plan.
As expected 
Predictable and this will take months
Does not make you better than someone with free plan
Attn @devingu and @AleksiAlkio
Thanks for letting me know. I will try to read through the conversation and escalate this further to a different agent.
Update: we’ve escalated the ticket to the AppSheet Eng team for further investigation. At the same time, we are treating agents not thoroughly reading through the conversation history very seriously. We are taking this as a lesson learned and discuss improvements within to address this ASAP.
Thanks @devingu for the update.