hi there. an issue started yesterday that is quite peculiar to me.
I have my last.fm account linked to my plex account to enable scrobbling of my listens through plexamp. I use plexamp on my iOS device but I also use the MacOS app.
yesterday, plexamp on MacOS began repeatedly scrobbling the same song every 15 seconds, despite the fact that I was not listening to this song at the time. it scrobbled over 2700 times until I was day-limited on last.fm having reached the maximum amount of scrobbles in a day.
meanwhile, the mobile app continues to scrobble normally.
steps I have taken:
I have quit the plexamp app. the constant scrobbling stops. I restart the app. no scrobbles happen until I press play, and then they resume every 15 seconds like clockwork.
I have deleted and reinstalled the plexamp app. same behavior as before. first time I open the app, no scrobbles happen until I press play, and then every 15 seconds (even if I re-pause playback) until I quit the app.
I have unlinked and relinked my last.fm and plex accounts. same behavior as before.
I have changed my last.fm password. no change.
potential side issue that may or may not be related at all:
I have noticed at some times in the past, when I am viewing a film within the plex web client, my firefox lastfm plugin will repeatedly try to scrobble some unknown thing every second while the video is playing.
is there any assistance anyone can give me? it does not appear to be an error with last.fm itself, something within plexamp and the last.fm plugin is not working correctly, or is stuck.
Given that you’ve deleted the Plexamp app and reinstalled, it can’t be the offline play history cache at play here, which is what I would have otherwise suggested.
You do however have a Firefox Last.fm plugin which is suspicious potentially. If you unlink last.fm from Plex (and don’t relink it), does the issue still occur?
as for the plexamp app, I literally dragged it to the trash and emptied the trash, and then re-downloaded (the same version) from the website. just to make that clear. I later deleted the cache as I said above.
when I unlinked last.fm from plex in my steps above, no scrobbling happened from plexamp at all. when I relinked the accounts, the auto-scrobbling began again immediately without me un-pausing playback.
could there perhaps be some order in which I should do things to perhaps sever whatever string of events are happening? or perhaps do a more thorough deleting of plexamp user files etc than I have done?
these are just the scrobbles that showed up when I opened plexamp to recreate the issue. I paused playback a few seconds after starting it, and as you see the scrobbles continued. I really appreciate the attention given to my issue
unfortunately this problem remains and as it is, it prevents me from using plexamp as I would like. I’m very open to hearing any additional strategies anyone has for me to eliminate this annoying thing.
apologies, i haven’t been able to look yet. you can delete your app data directory for Plexamp and cache directory and i suspect this will fix the issue.
thank you so much. I did not want to presume your urgent assistance in this kind of time frame, was just sourcing any potential other thoughts.
for the record, your step appears to have worked a charm. thank you so much! I’ve set aside copies of the two folders you mentioned, in case you want to look at them later. I’ll keep them for a week or so, and if you reply to this thread I’ll send them along.
really appreciate your help! I will report back to my support thread on this issue on last.fm with the steps I took, in case anyone else experiences this.
very sorry to say this issue has started back up again as of today. I will delete the same folders again but thought you’d like to know this doesn’t appear to be a one-off thing.
Actually, now that I’m looking at the logs again, your media server is returning a 500 for a request which I wouldn’t expect to fail.
Any chance—if you’re reproducing the problem live—that I can have server logs to match Plexamp logs? I can’t seem to see why the server would return a 500.
I should say those logs are from just now. the problem is not currently happening. I don’t know how to reproduce the problem except to wait a few days to see if it pops up again. if it does, then I’ll grab the server logs while it’s going on and add them to this thread.
Thanks, the new version should fix it (but still doesn’t explain the 500 returning from the server). It’s a workaround for a server apparent weirdness, basically.
