[GH-ISSUE #145] " Invalid authorization code" issue on Mobile (Android) #90

Closed
opened 2026-02-27 19:25:59 +03:00 by kerem · 2 comments
Owner

Originally created by @lu3do on GitHub (Nov 29, 2018).
Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/145

Since this month (exactly November 1st) I'm receiving a high number of " Invalid authorization code" coming from mobile users.

I'm aware of the recent issue with the wrong authentication endpoint.
https://github.com/jwilsson/spotify-web-api-php/issues/143
But this seems to be a different issue.

It seems to happen mostly on mobile devices running on Android, and almost all of them using Chrome mobile.
xnqo8fmj

I actually contacted the Spotify developers first, but they told me to open a issue here.

Originally created by @lu3do on GitHub (Nov 29, 2018). Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/145 Since this month (exactly November 1st) I'm receiving a high number of " Invalid authorization code" coming from mobile users. I'm aware of the recent issue with the wrong authentication endpoint. https://github.com/jwilsson/spotify-web-api-php/issues/143 But this seems to be a different issue. It seems to happen mostly on mobile devices running on Android, and almost all of them using Chrome mobile. ![xnqo8fmj](https://user-images.githubusercontent.com/482346/49192454-0143cb00-f330-11e8-9296-62fdc99b7abe.jpg) I actually contacted the Spotify developers first, but they told me to open a issue here.
kerem closed this issue 2026-02-27 19:25:59 +03:00
Author
Owner

@jwilsson commented on GitHub (Nov 29, 2018):

Hmm, I have no idea what could be causing that. Have you been able to reproduce it? Do you know of any other changes to your tech stack that happened around November 1? Are you using some PHP framework etc.?

If we can find the cause and it's something in this library, I'll of course be happy to fix it/accept a PR fixing it. But for now, I'm at a loss

<!-- gh-comment-id:442970248 --> @jwilsson commented on GitHub (Nov 29, 2018): Hmm, I have no idea what could be causing that. Have you been able to reproduce it? Do you know of any other changes to your tech stack that happened around November 1? Are you using some PHP framework etc.? If we can find the cause and it's something in this library, I'll of course be happy to fix it/accept a PR fixing it. But for now, I'm at a loss
Author
Owner

@jwilsson commented on GitHub (Mar 26, 2019):

Closing this due to a lack of activity.

<!-- gh-comment-id:476810286 --> @jwilsson commented on GitHub (Mar 26, 2019): Closing this due to a lack of activity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-web-api-php#90
No description provided.