bug: YTMusic detects activity but no tracks

[cm-burgos]

Please check existing knowledge before opening an issue

• I have checked the FAQ and documentation
• I have searched through existing issues and discussions.

Describe the Bug

I have multi scrobbler set up to scrobble from ytmusic to lastfm for two different users. Everything was working well for about a month.
This week one user got prompted to change her google password and after she did that, I changed the cookie for her ytm source. It stopped scrobbling for her about one day after that, then I changed it again gettting the cookie from a private session, there's no error fetching the data. It detects activity in ytm but no tracks are discovered even though she is in fact playing music.

For the other user things are working as usual and haven't stopped

Platform

Docker

Versions

• multi-scrobbler 0.9.11 on docker
• source: ytm
• client: lastfm

Logs

[2025-09-25 20:54:15.533 +0000] DEBUG  : [App] [Sources] [Ytmusic - silv-ytm] Last activity was at 20:51:50+00:00 (02:24 ago) | Next check in 10.00s | No new tracks discovered

[2025-09-25 20:54:05.272 +0000] DEBUG  : [App] [Sources] [Ytmusic - silv-ytm] Last activity was at 20:51:50+00:00 (02:14 ago) | Next check in 10.00s | No new tracks discovered

[2025-09-25 20:53:54.985 +0000] DEBUG  : [App] [Sources] [Ytmusic - silv-ytm] Last activity was at 20:51:50+00:00 (02:04 ago) | Next check in 10.00s | No new tracks discovered

[2025-09-25 20:53:44.560 +0000] DEBUG  : [App] [Sources] [Ytmusic - silv-ytm] Last activity was at 20:51:50+00:00 (01:54 ago) | Next check in 10.00s | No new tracks discovered

Additional Context

No response

[jj3os]

Where is the music being played? Sometimes the activity on the mobile apps (iOS/Android) is not recorded on the play history of the account. This has happened to me in the past.

To verify, check the history on the account's activity (https://myactivity.google.com/product/youtube?utm_source=my-activity), if the tracks played are not there, then MS can't update, as there's effectevily no data to fetch.

If that's the case, make sure the apps are on the latest versions and the history is enabled on the account profile.

[Ovyerus]

The same's been happening to me since setting up multi-scrobbler recently. No auth errors, just failing to find new tracks. Clicking "See Recent from Source API" says there's no recently played tracks either, so it seems like it could be some sort of problem with scraping the history page.