How does the app update, and what if it looks out of date?

How updates arrive

• When the app loads with a connection. Opening the app, or reloading the page, is when it looks for a new version.
• In the background. The new version is downloaded while you keep using the current one.
• With one automatic reload. As soon as the new version is ready, the page reloads by itself and opens on the same screen.
• Not without a connection. The version already on your device keeps working, and the update follows the next time the app loads online.
• An update can arrive while the app stays open. The app has no periodic update check of its own, but the browser may check too. Reopening with a connection is a useful way to check again, not a guarantee of immediate delivery.

What an update keeps

The table, the game being recorded and changes waiting to be sent are stored separately from the app’s own files, so an update leaves them alone. The same goes for being signed in and for the copy of your History, Statistics, Friends and Decks.

When the app looks out of date

1. Open Play and look under Service. Still to sync: or Needs attention means changes are waiting or were refused; handle those first (see check pending sync and recover rejected changes).
2. Make sure you have a working connection.
3. Close the app completely: swipe it away in the app switcher, or close the browser tab. Then open it again.
4. Wait a moment on the counter or on Play. If there is a new version, the app reloads once by itself.
5. Still the old version? Close and reopen it once more; now and then one extra restart is needed.

Missing a screen that a help article describes? Many features only appear while you are signed in, under Club.

What not to do

• Do not clear website data or reinstall to force an update. Clearing data deletes the local table and unsent changes; uninstalling can also remove that storage. Reopening with a connection is safer.
• Do not deliberately close or reload while Recording without a safety net is shown. Keep the app open with a connection and check that the result reaches History. Automatic updates are not blocked by this warning, so note the result separately if it cannot be sent.
• Do not sign out to fix it. Signing out does not update the app and does not send waiting changes.

If something seems wrong

• The app reloaded by itself during a game. An update may have caused it. Normally saved table data stays; check the life totals before continuing. Changes held only in memory after a storage failure may be lost.
• The installed app stays on an old version. Open it with a connection now and then. An app that is only ever opened without reception cannot update.
• It still looks old after a few restarts with a connection. Wait and try again later rather than deleting anything; nothing is lost by staying on the previous version for a while.