Spotify API doesn't always redirect to my app after successful login

[luis6674]

The issue we're talking about here is related to the web, not to the Spotify app. You create a website where you can login using your Spotify account (as described in the Authorization Code Flow docs). When the users clicks to log in with Spotify, they're redirected to the Spotify website, which authenticates them and then returns them to the original site (to the provided Return URI).

This works fine in every set up except one (at least that I'm aware of), which is when you go to the original website using Safari on an iPhone (up to date versions of Safari and iOS) *and* in that Safari browser you're not already logged in to Spotify. Then when you're redirected to the Spotify website you're asked to enter your credentials. And after doing so you should be authenticated and redirected to the original website. But instead, you're not redirected and just stay in the page posted in the screenshot above.

A video of this would not show anything except what I've described above and it will end in the screenshot posted above.

I hope this helps to reproduce the problem and look into it.

[jjacoba]

Hi Maria/Oscar,

See attached videos.

Chrome (Incognito):

https://www.youtube.com/watch?v=46IsXmthbpA

Safari (Private):

https://www.youtube.com/watch?v=ljDNZeYrtX4&t=20s

As you can see, it's the same URL i'm using (https://listening-stats-jn.netlify.app/) - Chrome, Brave and Firefox all redirect back to my app after authentication whereas Safari just takes me to https://accounts.spotify.com/en/status where I can see the account overview CTA even though it's using the same authorization code flow.

I hope this helps. If you need anything else let me know.

Thanks

Jacob

[Jdev99]

I’m having an issue where iOS currently redirects back to position in app after Spotify credentials are submitted, but android redirects back to the main app login page.. anybody know how to fix this issue? 

[NSueiro]

Same issue here. Has anyone find a solution or should we wait for Spotify to fix this?

[yourfriends]

Hi, we're encountering this bug also, and weren't able to find a solution online.