Constantly recurring database updates with v3.3

[robbely]

Describe the bug Whenever I start playnite with this update, I have a dialog "Downloading data from installed games" which occurs each time. Also when I change selected game I have a dialog "Database migration" which occurs each time.

To Reproduce Open playniite with addon v3.3 installed. Change selected game.

Expected behavior The first dialog makes sense, but I would expect it to only occur once, when starting for the first time after updating to 3.3 The second dialog I would have expected to not be there as migrations should have taken place during the first dialog.

Screenshots N/A

Extensions log N/A - I have uninstalled the addon for now as the updates and issues ares taking up too much time for me.

[ccrowles]

Same issue here, unfortunately. Every time that I start Playnite, if the option "automatically import for installed games" is turned on, instead of downloading data of newly installed games SuccessStory re-downloads the data of all installed games (which in my case are a lot, so this makes Playnite unusable for me for five minutes...).

As it can be seen, it says "SuccessStory: Downloading data from new games", but none of the games are new, and the data gets redownloaded at every Playnite startup.

Logs: playnite.log extensions.log

[veksha]

same. also Epic achievements dont work with 3.3

[ccrowles]

The issue still occurs for me on SuccessStory 3.3.1 (I updated it today, so I assume it should have been the fixed version?).

[CrashSpyro]

There's a way to prevent that, just uncheck Automatically Import data like the picture above

[ccrowles]

There's a way to prevent that, just uncheck Automatically Import data like the picture above

But the "automatically import data [when library is updated]" specifically says "(only new)", so it's still a bug because it tries to import everything. Unless you mean disabling the "automatically import for installed games" but again that would mean that the bug already mentioned in this issue thread is still present and that disabling is just a temporary workaround.

[sovalyeler]

Using SuccessStory 3.3.1. The issue still exists.

[ccrowles]

I hope the dev reopens this issue thread because the problem, as showed by multiple people, has not been fixed unfortunately.