Issues with LB-compatible channel since beta 7

Listening Post
1

I noticed last night that my scrobbles from Listening Post weren’t showing up on their destinations. After reviewing the LP logs, it looks like no scrobbles have been posted since late in the day on March 6th, which coincides with when I would have downloaded LP beta v7. During that time, tracks have continued to be recognized by LP and added to the log, but apparently not posted.

All of my LP scrobbles are sent to Multi-Scrobbler using the ListenBrainz submission format, which then distributes them to other sources. I attempted to verify the connection to Multi-Scrobbler, but nothing seemed to happen when I clicked the verification button. So I thought maybe I could get the flow restarted by re-entering my token. I deleted the old token and when I pasted it in again, I received this error message:

“Network error: Response could not be decoded because of error. The data couldn’t be read because it isn’t in the correct format.”

Could be a problem on my end, but I can’t figure out what it would be if that’s the case. Any ideas? Is there a way for me to view LP’s logs to check for failed connection attempts?

Listening Post v2026.0.11 (Beta 11)
2

Thanks for the report, @jacksaturn. Very quick answer¹: Click the “Contact the author” link in the main Help menu, this’ll generate a diagnostics report for you. You can send it over and/or read it yourself.

Hope that helps!

¹) It’s late, it’s the weekend…

1 Like
3

Thanks for this guidance! The diagnostics confirmed that no scrobble had been successful since March 6th, and the last three error reasons were “LB-compatible channel has not been configured.” So I’m guessing that something broke the configuration when I updated to beta v7.

The errors I was getting after trying to reset the config yesterday turned out to be because I had a trailing forward-slash on the end of the API Base URL. (I had taken the opportunity to change the old IP address I was using with a new, local DNS URL I set up.) With that slash removed, I’m successfully able to scrobble to Multi-Scrobbler again.

In the future I’ll make it a point to do a test scrobble each time I update to a new version! :+1:

4

Thanks for the update!

Good data point, I need to make the app surface issues like that better, not just in the log.