Skip to content

fix: Login with spotify throwing error #9726

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: alpha
Choose a base branch
from

Conversation

rahulsaps29
Copy link

In Spotify.js, getAccessTokenFromCode API is returning response object, which is passed to getUserFromAccessToken which parsing access_token in BaseAuthCodeAdapter, due to which it is throwing error - Spotify API request failed (from SpotifyAdapter line 79).

In Spotify.js, getAccessTokenFromCode API is returning response object, which is passed to getUserFromAccessToken which parsing access_token in BaseAuthCodeAdapter, due to which it is throwing error - Spotify API request failed (from SpotifyAdapter line 79).

Signed-off-by: Rahul kumar Singh <[email protected]>
Copy link

The branch release can only be set as base branch by members of @parse-community/core-maintainers.

Pull requests are usually opened against the default branch alpha, which is the working branch. Different repositories may have base branches with different names. If you are sure you need to open this pull request against a different branch, please ask someone from the team mentioned above.

@parse-github-assistant parse-github-assistant bot changed the base branch from release to alpha April 21, 2025 17:10
Copy link

parse-github-assistant bot commented Apr 21, 2025

🚀 Thanks for opening this pull request!

@rahulsaps29 rahulsaps29 changed the title Fix - spotify throwing error fix: login with spotify throwing error Apr 21, 2025
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title fix: login with spotify throwing error fix: Login with spotify throwing error Apr 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant