Official app does not submit scrobbles

  • 5
  • Problem
  • Updated 4 years ago
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: This conversation has been inactive for over 6 months and is now closed.

Since the site update, I cannot seem to scrobble tracks via the official Last.fm Scrobbler app. It only caches the listens and does not submit them via the API. It can successfully connect to the server though, or at least it says so. The "Reconnect" button does not help. See the screenshot of the Diagnostics view:



I am using the old version of the Scrobbler but it worked just fine three weeks ago. I am not aware of any API changes which might have broken this which is why I find it really strange.

Is this going to get fixed? I really hope my 500 scrobbles won't get lost. I would try upgrading the app but I'm too afraid of losing the cache.
Photo of prague.panda

prague.panda

  • 9 Posts
  • 5 Reply Likes
  • worried

Posted 4 years ago

  • 5
Photo of prague.panda

prague.panda

  • 9 Posts
  • 5 Reply Likes
I looked at the log file of the Scrobbler app and found this strange log:

[150830 19:49:09] "150830 19:49:09" - "-1607855704" - void ScrobblerManager::scrobble(TrackInfo) ( 105 ) - L4   "Foals – Lonely Hunter" 
[150830 19:49:09] "150830 19:49:09" - "-1607855704" - void ScrobbleCache::write() ( 349 ) - L4
   Wrote 470 tracks to "/Users/jankuca/Library/Application Support/Last.fm/jankuca_submissions.xml" 
[150830 19:49:09] "150830 19:49:09" - "-1607855704" - void ScrobblerManager::scrobble(const ScrobbleCache&) ( 126 ) - L4
   "jankuca" 
[150830 19:49:09] "150830 19:49:09" - "-1607855704" - void ScrobblerManager::scrobble(const ScrobbleCache&) ( 148 ) - L4
   No scrobbler available for: "jankuca" 

("jankuca" is my last.fm username obviously.)
Photo of prague.panda

prague.panda

  • 9 Posts
  • 5 Reply Likes
Reinstalling the Scrobbler app (while having a backup of the submission cache which I then returned to the original location) did not help. I'm still getting the same message.
Photo of prague.panda

prague.panda

  • 9 Posts
  • 5 Reply Likes
It looks like the support for this old version of the Scrobbler has been dropped as the API now returns 404 for many required API requests such as the pwcheck.php or xmlrpc.php. I dug into the inner workings of the old scrobbler and managed to build a service which fixes the scrobbling issue.


If anyone is having the same issue as I was, add the following line to your hosts file (/etc/hosts or C:\Windows\system32\drivers\etc\hosts):
23.21.201.35    ws.audioscrobbler.com
If that does not work, try entering the IP address to your web browser. If it redirects to audioscrobbler.com, let me know, otherwise look for the current IP address of the service using the following command, the IP address might change over time:
ping lastfm-api1-fix.herokuapp.com

What this fixes (for the Last.fm Scrobbler App v1.x.x.x):

  • Scrobbles being cached and never successfully submitted.
  • Users unable to log in or re-log in after a password change. (App was saying auth info is incorrect.) — It actually skips the check on save which allows the app to save the credentials. It does not introduce a vulnerability as the credentials are still being checked on every subsequent API request. You are just simply not notified of incorrect credentials on save, sorry about that.
  • Artist and track info not being displayed in the app. — There are a few issues such as the app now always shows there are 0 plays for every artist. This might get fixed.

It might look dangerous as this changes the server to which other Last.fm API requests are made. The service returns a 307 redirect for requests which do not need any modifications.This keeps the current working API intact.
(Edited)
Photo of Claw

Claw

  • 82 Posts
  • 118 Reply Likes
I had the same problem just yesterday. What did it for me was simply changing the connection setting from automatic to manual. Left all the fields blank and it worked.

This conversation is no longer open for comments or replies.