-
Notifications
You must be signed in to change notification settings - Fork 41
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
"Unable to download switch titles db" #91
Comments
The link is still valid (https://tinfoil.media/repo/db/titles.json), can you attach the logs ? |
2022-09-03T12:41:50.849+0100 INFO nsp-update/main.go:39 [SLM starts] |
To give this some context, I think at some point I knew there were some new things (updates/dlc) that were out but weren't present in the db, so I assumed it wasn't being able to update titles db or versions db, so I deleted my local files to see if it would download them again like on a fresh install, and it errored out. But it looks like if there is no settings file in the SLM folder then it downloads these files okay, and presumably it updates them afterwards since it's checking for differences between the local and remote file, but bizarrely if you have a settings json AND no title db, then it spits out an error. All in all it appears to be a minor issue that only affects people who delete their title db and not their settings. My bad. |
Thanks for the additional info, will look into this bug, happy to hear its working for you. |
@giwty long time no see... as I mentioned here #87 (comment) the author of titledb is using a new standard file and does not guarantee that the ones SLM currently grabs will always work therefore it is recommended to point SLM to the new standard files. |
Yep, will modify to use the ones from github, thanks |
If I had to guess it's because at some point blawar removed the file from his repo altogether, and it now requires you to run NUT to generate it.
Could use an update to rely on a different source for titles.json, or implementing NUT into the program or something.
The text was updated successfully, but these errors were encountered: