Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Authorization stuck after getting token

Authorization stuck after getting token

Hi everyone! I had my project up and working fine on localhost, but in moving it over to netlify, I think I messed something up? The user is able to access the authorization, and it seems like it's going through, and then the app stops when it reaches the url "examplename.netlify.app/callback#access_token=BQAaw.....YZafY&token_type=Bearer&expires_in=3600". The page displays a "Page not found" error. 

Does anyone know why it's getting stuck here? And how I can circumvent it?

 

Thanks!

Reply
6 Replies

A howlin' hello to you, siebraun!

It sounds like the issue could be related to the redirect URI in your Spotify API settings. When you register your app with the Spotify API, you need to specify the redirect URI that Spotify should send the authorization token to once the user grants permission.

If the redirect URI in your Spotify API settings doesn't match the URI of your Netlify app, then Spotify will not be able to send the authorization token back to your app, which can cause the authorization flow to get stuck.

To fix this issue, you should update the redirect URI in your Spotify API settings to match the URI of your Netlify app. You can do this by logging into your Spotify Developer Dashboard, finding your app, and then updating the Redirect URIs field under the App Settings tab.

Make sure to also update the redirect URI in your app's code to match the new URI in your Spotify API settings. This should allow the authorization flow to complete successfully and prevent it from getting stuck at the callback URL.

I'll be barking up the wrong tree without updates!

 

-Prague the Dog

Hi! Thanks for your quick reply!

I thought that might be the issue, but I've double and triple checked that they're the same, and the problem persists. ๐Ÿ˜ž Any other ideas are greatly appreciated!!!!

an update: it's no longer working on localhost either, even after I change all of the uri's and site links. Feeling antsy, as this is for a school project and is due very soon ๐Ÿ˜ญ๐Ÿ˜ญ๐Ÿ˜ญ Not sure what happened. Everything was fine a week ago. Any ideas are super appreciated

Did you ever figure it out?

ๆˆ‘ไนŸ้‡ๅˆฐไบ†ๅŒๆ ท็š„้—ฎ้ข˜๏ผŒไฝ ๆœ‰่งฃๅ†ณๆ–นๆกˆๅ—๏ผŸ

 

Iโ€™ll be boned if we donโ€™t resolve this folksโ€ฆ.
First, confirm that all URIs and site links are updated correctly, including localhost. Check for any recent changes in your code that might have affected the authentication flow. Additionally, ensure there are no typos or inconsistencies in your configurations. It could be helpful to review any recent updates to dependencies or frameworks that might have caused compatibility issues.

 

If all effected users could share more information on this predicament that would be greatly appreciated, it will also assist in narrowing down the culprit. 
I might be barking up the wrong tree without any updates,

 

-Prague the Dog

Suggested posts

Type a product name