[GH-ISSUE #24] Client mode may be broken #14

New issue

Closed

opened 2026-02-27 20:07:41 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 20:07:41 +03:00

Owner

Originally created by @tomballgithub on GitHub (Sep 19, 2025).
Original GitHub issue: https://github.com/misiektoja/spotify_monitor/issues/24

Starting today, my instance using client login stopped working with:

Error: Access token not found in response

A 2nd exported response body from a different account, that used to work (and generated a month after the first), also gives the same error.

I wasn't able to export a new one with proxyman with these methods:

Nothing special besides proxyman
Used the proxyman proxy
Blocked port 443 for spotify via OS firewall

I was able to do it via:

Running an old version.

But now I receive:

Error: client or refresh token may be invalid or expired!
Access token not found in response

Those were actually errors from spotify_profile_monitor, here's the current error for spotify_monitor:

Error, retrying in 3 minutes: Access token not found in response
Error: client or refresh token may be invalid or expired!

And I did the capture and export and test process twice

Originally created by @tomballgithub on GitHub (Sep 19, 2025). Original GitHub issue: https://github.com/misiektoja/spotify_monitor/issues/24 Starting today, my instance using client login stopped working with: * Error: Access token not found in response A 2nd exported response body from a different account, that used to work (and generated a month after the first), also gives the same error. _I wasn't able to export a new one with proxyman with these methods:_ - Nothing special besides proxyman - Used the proxyman proxy - Blocked port 443 for spotify via OS firewall _I was able to do it via:_ - Running an old version. _But now I receive:_ * Error: client or refresh token may be invalid or expired! Access token not found in response _Those were actually errors from spotify_profile_monitor, here's the current error for spotify_monitor:_ * Error, retrying in 3 minutes: Access token not found in response * Error: client or refresh token may be invalid or expired! And I did the capture and export and test process twice

kerem closed this issue

2026-02-27 20:07:41 +03:00

kerem commented

2026-02-27 20:07:42 +03:00

Author

Owner

@tomballgithub commented on GitHub (Oct 12, 2025):

Both @misiektoja and I verified this was broken when reported, but it seems that it is working again. I was able to use two response_bodies that I had saved off and they worked just fine.

@tomballgithub commented on GitHub (Oct 12, 2025): Both @misiektoja and I verified this was broken when reported, but it seems that it is working again. I was able to use two response_bodies that I had saved off and they worked just fine.

kerem referenced this issue

2026-02-27 20:07:47 +03:00

[PR #14] [MERGED] Missing * #26