[Spotify Player] Error upon usage of any command: read ECONNRESET

[robigan]

Extension

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

Description

Hello world!

I seem to be having an issue on my installation of Raycast and Spotify Player whereupon usage of any command I get a read ECONNRESET error. I have attempted to debug the issue myself, but I am not quite familiar with Raycast to get further debug information and the logs don't seem to be showing anything of interest. The browse all command worked the first time I used it after I restarted my Macintosh, but subsequent attempts resulted in the same issue. I am willing to submit a PR if someone directs me as to how to debug the extension, ideally if anyone can explain how I can hook a debugger into Raycast.

Steps To Reproduce

1. Restart machine
2. Use any spotify player command
3. Get successful results
4. Esc out of it and retry
5. Get a read ECONNRESET error

Current Behaviour

Ambiguous read ECONNRESET error

Expected Behaviour

Expected for the extension to work and not error out

[raycastbot]

Thank you for opening this issue!

🔔 @mattisssa @dillionverma @andreaselia @stuart @tonka3000 @dancannon @sxn you might want to have a look.

💡 Tip: Once the issue is resolved, comment @raycastbot close this issue to close it.

[robigan]

Related to thelinmichael/spotify-web-api-node#424

After some digging, a similar issue seems to have been tracked in the Node.js package oauth in issue jaredhanson/passport-oauth2#163. Unfortunately, the only issue I seem to have found that mentions this in spotify-web-api-node is stale and was first reported ~2y ago. Although spotify-web-api-node doesn't use any libraries that have tracked this similar issue, so I'll try investigating what causes the issue and might need to be patched.

[raycastbot]

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 😊

[raycastbot]

This issue has been automatically closed due to inactivity.

Feel free to comment in the thread when you're ready to continue working on it 🙂

You can also catch us in Slack if you want to discuss this.