raycast / extensions

Everything you need to extend Raycast.
https://developers.raycast.com
MIT License
5.03k stars 2.76k forks source link

[Spotify Player] Add "user-read-playback-position" scope #12404

Open rsefer opened 1 month ago

rsefer commented 1 month ago

Extension

https://www.raycast.com/mattisssa/spotify-player

Description

In hopes of adding the ability to show podcast episode played status (Pull Request incoming), I am hoping we can add the "user-read-playback-position" scope to the Spotify oauth api access. This allows us to determine whether or not an episode has been played (and at what position). This change needs to be made on the spotify developer account that contains the client ID.

Who will benefit from this feature?

All users

raycastbot commented 1 month ago

Thank you for opening this issue!

🔔 @mattisssa @peduarte @sxn @dillionverma @andreaselia @stuart @tonka3000 @dancannon @pernielsentikaer @stevensd2m @erics118 @hjoelh @hobhouse @bkeys818 @jatindotdev @the-devbear you might want to have a look.

💡 Author and Contributors commands The author and contributors of `mattisssa/spotify-player` can trigger bot actions by commenting: - `@raycastbot close this issue` Closes the issue. - `@raycastbot rename this issue to "Awesome new title"` Renames the issue. - `@raycastbot reopen this issue` Reopens the issue. - `@raycastbot assign me` Assigns yourself to the issue. - `@raycastbot good first issue` Adds the "Good first issue" label to the issue.
rsefer commented 1 month ago

Upon review, I realize there may not be a need to enable this scope in the developer account (but will definitely be required in code). Strangely, however, when I add the scope in code with the existing Client ID, I get an "Illegal scope" error from Spotify when trying to complete the Oauth flow.

image

When I do the same using my own newly created Client (ID), the Oauth works fine. For what it's worth, I have both the Web API and the Web Playback SDK enabled on my client. Hope that provides more context.

image
raycastbot commented 2 days ago

This issue has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 10 days to keep our backlog clean 😊