Skip to content
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

Error when searching Ludusavi for games to import (List no longer searchable) #282

Closed
redactedscribe opened this issue Jul 20, 2022 · 2 comments
Assignees
Labels
Milestone

Comments

@redactedscribe
Copy link

Not sure why this is happening now because it previously functioned as expected, but when I search the Ludusavi list, I get:

---------------------------
Game Backup Monitor
---------------------------
An error has occurred during Ludusavi data conversion.



Object reference not set to an instance of an object.
---------------------------
OK   
---------------------------
---------------------------
Game Backup Monitor
---------------------------
This list does not contain any new games to import.
---------------------------
OK   
---------------------------

I lost Internet connection during the first time I encountered the issue and there was actually a third popup box which appeared (before the other two):

---------------------------
Game Backup Monitor
---------------------------
An error has occurred reading the text file.



Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
---------------------------
OK   
---------------------------

It is no longer possible to search and therefore import any manifests from Ludusavi.

Maybe I need to delete some file so that a fresh copy is fetched?

GBM 1.3.1
Windows 11

@redactedscribe
Copy link
Author

redactedscribe commented Jul 20, 2022

Found the answer: Deleting both "manifest.etag" and "manifest.yaml" files from %LOCALAPPDATA%\gbm on Windows and performing a new search caused them to be re-downloaded and now the Import Game Configurations window works as before.

I noticed that "manifest.yaml" was 0 bytes on disk prior to deletion, so it was probably that file alone that caused the issue.

@MikeMaximus
Copy link
Owner

MikeMaximus commented Jul 20, 2022

Thanks for the report. I'll update the error handling to delete the files automatically or change the order the etag is created so it doesn't get stuck that way after a download failure.

The issue was that the etag file was being created/updated regardless of if the download failed. Since the etag matched the server, it was trying to use the empty cache file instead of downloading a fresh one.

I fixed that problem and some other flaws I noticed with the error handling when the list downloads fail.

@MikeMaximus MikeMaximus self-assigned this Jul 20, 2022
@MikeMaximus MikeMaximus added this to the 1.3.2 milestone Jul 20, 2022
MikeMaximus added a commit that referenced this issue Jul 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants