@Fabian,
I’m really sorry for not being responsive lately. I’m back on this issue now.
Could you please let me know which Chrome version you have installed on the device that is seeing this error? You can check the Chrome version by going to the Chrome setting page on your device.
Also, does it happens only to one of your users? Could you please let me know their AppSheet ID (either here or by mail to gil@appsheet.com).
It happened to me last week(wasn’t the first time). Clearing the cache won’t do it. Clearing all data works. This error is not frequent, it’s rather rare, but it’s a pain in the ass when it happens.
And you said that after clearing the app’s data (or reinstalling) the error is resolved but still can reoccur later, is that correct? How often does it happens?
Have you notice any pattern of under what conditions it happens? Is it only when the device is offline?
@Vlad_Roman, would you mind sharing your app’s name?
Yes, clearing the app’s data (or reinstalling) will resolve the error, but it can reoccur.
We think it reoccurs when we don’t use the phone for some days. Last time after 2 weeks vacation.
But the phone was restarted, it was also online and I set it to “Sync on Start”.
I’m having this issue too. I will ask users to clear data, but it is really not ideal. Destroys customers confidence in the solution. Especially if its going to keep happening, it make it hard for me to offer Appsheet as a solution.
We’re rolling out a number of updates to the offline launch mechanism now which we believe should resolve this. Previous attempts to fix it have identified particular problem scenarios but we would find later there were still others we missed. The latest round of updates will move to a different approach that we think will be more robust generally to this class of problem. If you find this keeps occurring though, please continue to let us know.
net::ERR_FAILED
The error only appears on SOME of our devices. The other devices (exactly the same model, Android version, software, etc) run perfectly.
So the issue is not with the Device, App or the version of Android, etc.
We have also restored factory settings on phones, updated Android, and reinstalled Appsheet multiple times. What is interesting is that with re-installation, the Appsheet App opens for the first time. BUT the next time you open the app the same error comes up and you’re stuck.
Hi, my client has been having this problem too. Actually, today he had one user with this problem. I told him to uninstall and install again and it got fixed. But it´s still a problem because it occurs sporadically and the users of this particular client are people who are not very familiar with smart phones, so any process of uninstalling and installing again is a real pain. Please help us to solve this! Thanks.
Perhaps useful to other people in the thread, or finding this thread…
This problem has now been solved for us. It seemed to be a related to Appsheet’s new IP addresses needing to be added to our SQL Server Firewall rules. That’s what we did and now Apps are good again.
I have installed the app I created on 2 mobile phones and 2 tablets. They work fine on the phones however they do not work on the android tablets. I have uninstalled and restarted the apps from the tablets on a couple of occasions and still seem to be having the same issue.
What happens is it installs and does not allow me to start the app instead it goes to the web browser asking me to sign in.