[GH-ISSUE #819] Option to update client id and key to avoid permission issue when upgraded from normal user to premium user #342

New issue

Open

opened 2026-02-28 14:48:36 +03:00 by kerem · 0 comments

kerem commented

2026-02-28 14:48:36 +03:00

Owner

Originally created by @avijit1258 on GitHub (May 19, 2021).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/819

I found an issue with spotify API keys. I have generated client id, key pair when I was normal user for spotify_tui. As a normal user, I could not access some feature. I then upgraded my account to premium. But still I faced not permitted error which is because the previous client id and key acts as normal user though I am premium now. The solution I found is to generate another pair of id, key after account status change. I have tested it by changing id, key pair in .yml file and it works like a charm. I have to options in mind to resolve the issue.

Trigger the first set up page if user wants that.
Have an option to update id, key pair.

I am following the repo for few days hoping to contribute. As I am new to the repo, having expert opinion about what can be best way to handle the issue can help me to create a PR.

Originally created by @avijit1258 on GitHub (May 19, 2021). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/819 I found an issue with spotify API keys. I have generated client id, key pair when I was normal user for spotify_tui. As a normal user, I could not access some feature. I then upgraded my account to premium. But still I faced not permitted error which is because the previous client id and key acts as normal user though I am premium now. The solution I found is to generate another pair of id, key after account status change. I have tested it by changing id, key pair in .yml file and it works like a charm. I have to options in mind to resolve the issue. 1. Trigger the first set up page if user wants that. 2. Have an option to update id, key pair. I am following the repo for few days hoping to contribute. As I am new to the repo, having expert opinion about what can be best way to handle the issue can help me to create a PR.