gsabater / backlog.rip

Free and open source library manager for all your games. Works in the cloud, without any launchers. Organize and manage your games with ease.
https://backlog.rip
10 stars 1 forks source link

Issues when scanning Steam library #26

Closed axewater closed 4 months ago

axewater commented 4 months ago

I scanned my huge library and it took long (makes sense) but I had no sense of progress. Maybe you can have an indicator (number of games found / processed) while it is scanning.

gsabater commented 4 months ago

Hey @axewater thanks for reaching out.

I agree with you, the user experience when loading games could be better. So i can understand a little better.

Thanks for your time

axewater commented 4 months ago

My library is 900 games. I actually had to reboot in between so it didnt finish (it ran for about 30 minutes) . I'll run it again and time it.

gsabater commented 4 months ago

@axewater This is pretty strange. The whole process shouldn't be more than a few seconds (10 max), and definitely you shouldn't have to reboot.

If you can, please open the developer console with F12 on your browser, and in the console and network tabs, you can send me a few screenshots, it would help a lot. IF you can, please, send them to me via discord https://discord.com/channels/@me/150726801969119233

I should definitely add checks and notify the user if something goes wrong, like in your case.

axewater commented 4 months ago

tried discord .. you link didnt take me anywhere. I think the issue may be Im on a corporate network, not all arbritary ports are allowed to connect directly to the outside. Here is the screenie:

backlog

Errors in browser console:

runtime-core.esm-bundler.js:259  TypeError: e.data.games.forEach is not a function
    at Object.prepare (importer.js:220:18)
    at aa0 (importer.client.js:164:35)
    at Object.ea0 [as scan] (importer.client.js:150:9)
    at async Proxy.scanAndPrepare ([platform].vue:1123:20)
YU1 @ runtime-core.esm-bundler.js:259

2steam:1  Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
axewater commented 4 months ago

ok this is super weird. i started clicking around the site because the index didnt seem to do anything. it says library 0 games, but then i clikc on it, it tells me again, you have nothing, go scan, but I click on browse games, and there ... i see a ton of my games!

bl2

top right corner still says '0 games' at the bottom of the screen:

Showing up to 196 of 844 results No games filtered

gsabater commented 4 months ago

@axewater

The discord problem might be mine, i don't know how to make a link to a dm, sorry.

According to your screens, I think the api didn't get any games , maybe you can open the console (F12) before clicking on scan library and follow the steps 1, 2 and 3 in this screenshot. Then click the scan button and you will have 4 and 5 with the response

image

axewater commented 4 months ago

it gave me this:

{fetch: {status: "success", data: []}, status: "success", steamid: "76561198030855100"}
fetch
: 
{status: "success", data: []}
data
: 
[]
status
: 
"success"
status
: 
"success"
steamid
: 
"76561198030855100"

so on your I see 200 games in the response, not on mine

gsabater commented 4 months ago

Hello @axewater In my end i can solve that the process don't fail if the response is empty. But I think that this might be related to some settings in your profile privacy settings.

Please, review this link

and then go to your profile privacy settings and tell me what you have

Here is mine for reference. I'd bet the "game details" option is the one giving problems image

Thanks again

gsabater commented 4 months ago

@axewater The issue is fixed, the problem was due to Steam IDs not being sent correctly by the server due to issues with big ints.

Anyway, i have added the following screens to improve the user experience based on your feedback

Thanks for your feedback


Fixed in release 0.11 Complete changelog in https://backlog.rip/changelog