search

wistoff / legacy-scrobbler

Legacy Scrobbler is designed to bridge the gap between legacy hardware, and the music platform Last.fm. It enables users to sync their listening history from offline devices to their Last.fm profile, preserving their music legacy in the digital era.
https://legacyscrobbler.software/
GNU General Public License v3.0
12 stars 0 forks source link

Failed to scrobble Tracks #2

Open mrondr opened 1 month ago

mrondr commented 1 month ago

Since yesterday evening, legacy-scrobbler shows a "Failed to scrobble Tracks" message.

Screenshot_20240520_104353

Tested versions: 1.0.0, 1.0.1 Attempts to solve the issue:

Is there any way I can try to debug this or provide some log?

wistoff commented 1 month ago

Are you connected to the internet? This usually happens when the request to the scrobble api fails.

Does the login work properly? You could also try to reset your config in the menu.

Unfortunately I didn't implement an advanced log output yet.

mrondr commented 1 month ago

Are you connected to the internet? This usually happens when the request to the scrobble api fails.

I can browse the internet no problem and I could log out and back in.

Does the login work properly?

I think so. I am shown the lastfm aut page and going back to legacy-scrobbler I can see my account icon and name

You could also try to reset your config in the menu.

I tried this and it seems everything goes smoothly. I am reporting the screenshot below.

Step 1 Screenshot_20240520_174603 Step 2 Screenshot_20240520_174631 Step 3 Screenshot_20240520_174654

If you thing it might help I can take my chances at trying to compile the project myself and trying to debug it although I am not super familiar with js or vue

mrondr commented 1 month ago

So, I gave it a try. Again, apologies if I am not doing something correctly. I have never worked with js before. I have tried to display the error directly in the error pop up and it seems that you are right, this appears to be a network error. Some other error appear in the terminal just before the app fails to scrobble but by googling them it seems they are more related to visualization stuff.

image

wistoff commented 1 month ago

Thanks for supplying the screenshots. Can you change devTools: false to true inside the main.js and run npm run start again? Then the app should open with the developer tools and print the full error in the dev tools console.

mrondr commented 1 month ago

So, now everything appears to works both when building from source with devTools: false and True and from release 1.0.1 on windows. The only thing that changed is the fact that in the meanwhile I have sync'ed my ipod on itunes. I don't know whether that flushed some kind of data that was problematic to scrobble or the fact that the successful test was performed by scrobbling one single song for each case (i.e., the size of the list of songs to scrobble played a part). I will investigate further, starting with a higher number of songs.

While testing, another ``odd'' behavior arose. After a list of songs is scrobbled, these songs still appears when refreshing the ipod. Is this the expected behavior? For instance, after syncing with iTunes: 1) I listen to two songs, then scrobble with legacy-scrobbler. The scrobble is successful. 2) I listen to one song, and open legacy-scrobbler. This is what I am shown.

Screenshot_20240521_154042

3) If I scrobble at that state, I am shown this screenshot, somewhat indicating that three songs have been scrobbled

Screenshot_20240521_152353

4) However, the scrobbling was performed correctly, that is, only the previously unscrobbled song was scrobbled and no duplicate scrobbles are present in my lastfm page.

image

wistoff commented 1 month ago

Okay nice that it works now. Have you been able to figure out what fixed the error?

The "odd" behavior you are describing is probably based on the following things:

  1. Your settings for "Automatic Delete": set this to true if you want that the songs are cleared from your iPod listening history after using the Scrobbler. This is set to false by default.
  2. All the songs you submit have a timestamp and can thus be only submitted once, that means there can be no duplicate scrobbles when the timestamp for that specific song is the same. Even if you submit it multiple times.
mrondr commented 1 month ago

Have you been able to figure out what fixed the error?

Unfortunately not yet. I have just scrobbled 14 songs without a hitch. No clue on what was going on yesterday as I really don't see any difference: I am scrobbling with the same release, same os, same machine, same internet connection. If it ever happens again I'll make sure to send you the devTools console log.

The "odd" behavior you are describing is probably based on the following things:

Thank you for clarifying this to me. I guess Automatic Delete = false is pretty valuable for those that after scrobbling also want to import their listening record to itunes. Makes a lot of sense.

Thank you for making such an awesome tool.

wistoff commented 1 month ago

Unfortunately not yet. I have just scrobbled 14 songs without a hitch. No clue on what was going on yesterday as I really don't see any difference: I am scrobbling with the same release, same os, same machine, same internet connection. If it ever happens again I'll make sure to send you the devTools console log.

It's possible that the problem was on my server ... I'm hosting the api myself and maybe the server had a short downtime. I'll make sure to check the logs. I'll close this issue for now. If the problem happens again please let me know and I'll investigate it further.

mrondr commented 1 month ago

Hi, here's the error with devTools: true

image