-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collection not saving #333
Comments
Thanks, I will look into it. |
So it only recreates the updated collection.json if you go at least once to the Collection tab in Firestone. Could you try opening the collection tab, then check if the collection.json gets updated when you go to Hearthstone's Collection Manager? |
Thanks for your fast response. Here are the steps I just tried. Open Hearthstone (HS), open FireStone (FS). Whenever FS and HS are both open, the collection tab in FS will eventually update. But it always opens with my old collection, keeps my old collection when HS is not open, and fails to update collection.json. (Which to me is rather inconvenient, because I use collection.json as input for my personal collection / missing dust tracker) |
Just to follow up, today I tried again and I noticed that collection.json does once more update when I expect it. I don't know whether this is due to something you did or due to some weird change on my end. But for now you can close this issue. (I will open a new one if it returns) |
Thanks for the update. If the issue returns you can just reopen this one (or wait a bit before closing it, I don't use GH issues as a way to track my work, so I don't mind if things are closed in a timely manner) |
Steps to reproduce:
The root cause seems to be that modifications to the collection are no longer saved to %appdata%\Overwolf\lnknbakkpommmjjdnelmfbjjdbocfpnpbkijjnob\collection.json. The last modified timestamp of this file does not change anymore, and when I delete or rename it, Overwolf shows an empty collection on startup, until it synchronizes, but does not create a new collection.json file.
The text was updated successfully, but these errors were encountered: