Guide updated
Read the save dot beside the original game’s account name and its message, then check the same sign-in identity on both devices. Green/saved means the last upload succeeded; saving or queued changes may still be local; offline waits for reconnection. “Saved only in this browser” is local mode, so waiting longer cannot produce a cloud transfer.
Read the save indicator before switching devices
Scroll sideways to read every column.
| Game message | Meaning | Result / next action |
|---|---|---|
| Saved in the cloud | Latest upload succeeded. | Now compare on the second device using the same account. |
| Saving… | An upload is running. | Keep the connection and wait for completion. |
| Saving… (queued or pending) | The same visible label also covers cached changes waiting for their scheduled cloud upload; it does not prove the upload has completed. | Stay online; finish safely and check for Saved in the cloud before relying on another device. |
| Offline: it will upload when you’re back | Cloud is unavailable; local cache remains. | Reconnect on this device; keep its site data and avoid parallel spending. |
| Saved only in this browser / Guest: not saved | Local mode / guest mode, not cloud sync. | Waiting longer cannot create a cloud save; use the original online game and intended account. |
Resolve the mismatch without discarding the source copy
Scroll sideways to read every column.
| What you see | What to do | Success / next step |
|---|---|---|
| Device B is older while A says Saving/Offline | Bring A online, keep its game open and site data intact, finish safely and wait for saved before spending on B. | B can then load the merged same-account state; compare owned entries and a known upgrade. |
| Both devices say saved but show different accounts | Match the original sign-in method and exact username/Google identity; do not merge unrelated identities by changing display nicknames. | Both are authenticated to the same account before a data comparison. |
| Cloud cannot initialize and login note says local | Open the original published HTTPS version and check connectivity/login. A downloaded file:// build or unavailable cloud configuration uses browser-local mode. | Use the mode note to distinguish local persistence from cloud sync; preserve the old local copy. |
What to record if synchronization stays pending
Keep the device with the last good collection unchanged. Record the game URL, account method, indicator/message, connection status and one concrete missing Pokémon or upgrade. Report that mismatch rather than clearing all browser data. This website’s collection tracker cannot read, upload or replace the original game’s save.
Open the next useful page
Related pages
Game data & sources
The linked game files show where these stats, costs and rules come from. Updates to the game may change them.
Data version: a9b21f09
- https://pokesurvivor.com/en/guide/
- https://github.com/JPTER78/pokesurvivor/blob/a9b21f091d7e2e0b10bc9ef94836447bf63cddeb/README.md
- https://github.com/JPTER78/pokesurvivor/blob/a9b21f091d7e2e0b10bc9ef94836447bf63cddeb/js/core/db.js
- https://github.com/JPTER78/pokesurvivor/blob/a9b21f091d7e2e0b10bc9ef94836447bf63cddeb/js/ui/ui.js
- https://github.com/JPTER78/pokesurvivor/blob/a9b21f091d7e2e0b10bc9ef94836447bf63cddeb/js/ui/login.js
- https://github.com/JPTER78/pokesurvivor/blob/a9b21f091d7e2e0b10bc9ef94836447bf63cddeb/js/data/changelog.js