Starting around 8PM PDT on Tuesday Aug 2 we saw a sudden increase in error logs of a particular error coming from mobile devices. Affected apps present with the following symptoms:
- The app appears to start successfully and displays the header and footer, but no content in the center.
- The header and footer buttons are visible but unresponsive.
Based on customer support issues with this presentation, it appears that restarting the app or the device does not help. We believe this is because the problem involves a resource that on mobile devices is persisted in the local cache. A few minutes ago we released a new build, which under normal circumstances should trigger an attempt to refresh this cache on the next app start (assuming a network connection is available). We arenโt certain whether this is still happening for apps in this broken state, but it may be worth trying the following if you or your users are among those affected:
- Fully close the app (swipe it out of the list of apps open in the background).
- Restart the app with a network connection.
- Leave the app open for a few minutes to allow enough time for new assets to download in the background.
- Fully close and restart the app again - if step 3 succeeded, it should start up with the new cache.
If this still has no effect, unfortunately clearing AppSheet data or reinstalling AppSheet may be the only way to break out of this state. Guidance for how to do that can be found here.
We believe this was a transient issue, but one that left affected users stuck in a persistent error state. The timing of the sudden increase in errors does not appear to correlate with any new release or system change from our end, and we are still investigating the root cause. In the meantime, we have a pending change that should prevent this particular error from happening again and will be taking steps to prevent this sort of problem more generally going forward.
LinkedIn
Twitter
