Legendary syncs in the wrong direction after update

[clst]

Platform

Operating system and version: Win7
Legendary version (legendary -V): legendary version "0.20.34", codename "Direct Intervention"

Expected Behavior

1. Game is updated with legendary
2. egl-sync --export-only should update egl

Current Behavior

legendary gets the old version information from egl

Steps to Reproduce

1. import updatable game
2. update game
3. run egl-sync --export-only

Additional information

Logs:

 * Gloomhaven (App name: 1bcd791d54684eb29ed32ad1c0593d12 | Version: 1.0.7321.0 | Platform: Windows | 16.58 GiB)
  -> Update available! Installed: 1.0.7321.0, Latest: 1.1.8307.0

legendary.exe update Gloomhaven
[DLM] INFO: Found 0 missing files.
[cli] INFO: Install size: 16977.58 MiB
[cli] INFO: Download size: 4508.21 MiB (Compression savings: 11.0%)
[cli] INFO: Reusable size: 33.05 MiB (chunks) / 11927.04 MiB (unchanged / skipped)
[...]
[DLManager] INFO: All done! Download manager quitting...
[cli] INFO: Finished installation process in 108.02 seconds.

legendary.exe egl-sync --export-only
[cli] INFO: Reading EGL game manifests...

Checking for exportable games...
Nothing to export.

Checking automatic sync...
Enable automatic synchronization? [Y/n]: n
[Core] INFO: App "1bcd791d54684eb29ed32ad1c0593d12" has been updated from EGL, syncing...

 * Gloomhaven (App name: 1bcd791d54684eb29ed32ad1c0593d12 | Version: 1.0.7321.0 | Platform: Windows | 16.58 GiB)
  -> Update available! Installed: 1.0.7321.0, Latest: 1.1.8307.0

[user4302]

This issue prompted EGL to redownload Fortnite (70gb) :l
stopping the download,
and then closing EGL,
deleting the files inside Fortnite/.egstore/bps
and Fortnite/.egstore/pending
and reopening EGL fixed the issue for me

[CommandMC]

This is somewhat of a complicated issue. When you run egl-sync, Legendary only sees that the version strings from it and the EGL differ, and concludes that you updated the game from the EGL. It doesn't know that the versions were just the same, you then updated, and that it should thus replace the EGL version.
It's not really possible to resolve this, as version strings have no schema of any kind, so you can't say "this version is newer, let's use that".

Enabling automatic sync would resolve this, as that'll make Legendary update the EGL version when you update a game through it