[GH-ISSUE #236 ] Fetching Problems: can´t fetching #933

Author

Owner

@LePetit45 commented on GitHub (Jan 6, 2026):

I have the same issue, impossible to fetch my public spotify playlist.

@LePetit45 commented on GitHub (Jan 6, 2026): I have the same issue, impossible to fetch my public spotify playlist.

kerem commented

Author

Owner

@Ramog commented on GitHub (Jan 6, 2026):

Search also doesn't seem to work, both with or without vpn

@Ramog commented on GitHub (Jan 6, 2026): Search also doesn't seem to work, both with or without vpn

kerem commented

Author

Owner

@skinnyrogers commented on GitHub (Jan 6, 2026):

can confirm as well... Fetch does not work as of last hour nor does search function from multiple OS & PC's

@skinnyrogers commented on GitHub (Jan 6, 2026): can confirm as well... Fetch does not work as of last hour nor does search function from multiple OS & PC's

kerem commented

Author

Owner

@wichos12 commented on GitHub (Jan 6, 2026):

Same issue here
[12:04:20]
[info]
fetching track metadata...
[12:04:20]
[debug]
url: https://open.spotify.com/intl-es/track/6y4yspeb68kgoai1dk130f?si=aed9c3e00ccd4288
[12:09:20]
[error]
fetch failed: failed to fetch metadata
[12:09:20]
[error]
failed to fetch metadata

@wichos12 commented on GitHub (Jan 6, 2026): Same issue here [12:04:20] [info] fetching track metadata... [12:04:20] [debug] url: https://open.spotify.com/intl-es/track/6y4yspeb68kgoai1dk130f?si=aed9c3e00ccd4288 [12:09:20] [error] fetch failed: failed to fetch metadata [12:09:20] [error] failed to fetch metadata

kerem commented

Author

Owner

@beeatrixistudy commented on GitHub (Jan 6, 2026):

Stopped working half way through my download list :(
[18:12:04]
[info]
fetching album metadata...
[18:12:04]
[debug]
url: https://open.spotify.com/album/0gsiszk6jwywaygvattud4?si=egdj-lpdrmqlqjz-s5oxtw
[18:17:04]
[error]
fetch failed: failed to fetch metadata
[18:17:04]
[error]
failed to fetch metadata

@beeatrixistudy commented on GitHub (Jan 6, 2026): Stopped working half way through my download list :( [18:12:04] [info] fetching album metadata... [18:12:04] [debug] url: https://open.spotify.com/album/0gsiszk6jwywaygvattud4?si=egdj-lpdrmqlqjz-s5oxtw [18:17:04] [error] fetch failed: failed to fetch metadata [18:17:04] [error] failed to fetch metadata

kerem commented

Author

Owner

@gaaash commented on GitHub (Jan 6, 2026):

same issue can't fetch or search but without any errors just stuck in fetching...

@gaaash commented on GitHub (Jan 6, 2026): same issue can't fetch or search but without any errors just stuck in fetching...

kerem commented

Author

Owner

@Ramog commented on GitHub (Jan 6, 2026):

same issue can't fetch or search but without any errors just stuck in fetching...

well it errors out after 5 minutes (probably the timout time on the request)?
are you sure it doesn't for you?

@Ramog commented on GitHub (Jan 6, 2026): > same issue can't fetch or search but without any errors just stuck in fetching... well it errors out after 5 minutes (probably the timout time on the request)? are you sure it doesn't for you?

kerem commented

Author

Owner

@LePetit45 commented on GitHub (Jan 6, 2026):

I ran a few tests directly on the Spotify API without going through SpotiFLAC, making the same fetching requests as the app, and I can confirm that it's just a timeout of the Spotify API.

@LePetit45 commented on GitHub (Jan 6, 2026): I ran a few tests directly on the Spotify API without going through SpotiFLAC, making the same fetching requests as the app, and I can confirm that it's just a timeout of the Spotify API.

kerem commented

Author

Owner

@gaaash commented on GitHub (Jan 6, 2026):

same issue can't fetch or search but without any errors just stuck in fetching...

well it errors out after 5 minutes (probably the timout time on the request)? are you sure it doesn't for you?

my bad, i got same errors like you after 5 min

I ran a few tests directly on the Spotify API without going through SpotiFLAC, making the same fetching requests as the app, and I can confirm that it's just a timeout of the Spotify API.

yes, i think it's a Spotify problem and they might restrict things after those scrape incidents they had

@gaaash commented on GitHub (Jan 6, 2026): > > same issue can't fetch or search but without any errors just stuck in fetching... > > well it errors out after 5 minutes (probably the timout time on the request)? are you sure it doesn't for you? my bad, i got same errors like you after 5 min > I ran a few tests directly on the Spotify API without going through SpotiFLAC, making the same fetching requests as the app, and I can confirm that it's just a timeout of the Spotify API. yes, i think it's a Spotify problem and they might restrict things after those scrape incidents they had

kerem commented

Author

Owner

@LePetit45 commented on GitHub (Jan 7, 2026):

I just found a workaround. Let me explain

In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it :

Get your client_id and secret_id from the spotify api dashboard (Some documentation here)
Clone the SpotiFLAC project and configure your environment to build and run the app
Change the client_id and secret_id variable, available in the backend/spotify_metadata.go, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file.
Build and run
Enjoy !

@LePetit45 commented on GitHub (Jan 7, 2026): ## I just found a workaround. Let me explain In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it : 1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps)) 2. Clone the SpotiFLAC project and configure your environment to build and run the app 3. Change the client_id and secret_id variable, available in the ``backend/spotify_metadata.go``, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file. 4. Build and run 5. Enjoy !

kerem commented

Author

Owner

@freeku commented on GitHub (Jan 7, 2026):

Thanks for the suggestion @LePetit45 , your workaround works indeed! For step 2, I had to download and install Go, Wails and PNPM, after that I could run the application using command wails dev

@freeku commented on GitHub (Jan 7, 2026): Thanks for the suggestion @LePetit45 , your workaround works indeed! For step 2, I had to download and install Go, Wails and PNPM, after that I could run the application using command `wails dev`

kerem commented

Author

Owner

@MYRWYR commented on GitHub (Jan 7, 2026):

Just to clarify to anyone who does use this "workaround" - your Spotify account will be banned, it's an eventuality. If you go this route, it's best to use a burner account's credentials.

@MYRWYR commented on GitHub (Jan 7, 2026): Just to clarify to anyone who does use this "workaround" - your Spotify account will be banned, it's an eventuality. If you go this route, it's best to use a burner account's credentials.

kerem commented

Author

Owner

@FrancoisDeBellescize commented on GitHub (Jan 7, 2026):

This is a rate limit issue with the Spotify account used so yes if you use your own it will allow you to make it work

Here is a log I've added to debug:

[warning] getJSON: rate limited for https://api.spotify.com/v1/tracks/2YOTWRGu8Y1u46i0cGL6gg, retrying after 24h0m1s

@FrancoisDeBellescize commented on GitHub (Jan 7, 2026): This is a rate limit issue with the Spotify account used so yes if you use your own it will allow you to make it work Here is a log I've added to debug: [warning] getJSON: rate limited for https://api.spotify.com/v1/tracks/2YOTWRGu8Y1u46i0cGL6gg, retrying after 24h0m1s

kerem commented

Author

Owner

@Silvergish commented on GitHub (Jan 7, 2026):

Just to clarify to anyone who does use this "workaround" - your Spotify account will be banned, it's an eventuality. If you go this route, it's best to use a burner account's credentials.

Oof. Yeah, I don't want to risk that. Hope another solution can be found. If not, it was fun while it lasted.

@Silvergish commented on GitHub (Jan 7, 2026): > Just to clarify to anyone who does use this "workaround" - your Spotify account will be banned, it's an eventuality. If you go this route, it's best to use a burner account's credentials. Oof. Yeah, I don't want to risk that. Hope another solution can be found. If not, it was fun while it lasted.

kerem commented

Author

Owner

@Silvergish commented on GitHub (Jan 7, 2026):

I just found a workaround. Let me explain

In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it :
1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps))

2. Clone the SpotiFLAC project and configure your environment to build and run the app

3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file.

4. Build and run

5. Enjoy !

I was going to look into this method, but it's way above my head. Haha. I don't know a lot about code. I mean, I can follow instructions if listed, but I would need a step by step guide. I'll just hope for a fix.

@Silvergish commented on GitHub (Jan 7, 2026): > ## I just found a workaround. Let me explain > > In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it : > > 1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps)) > > 2. Clone the SpotiFLAC project and configure your environment to build and run the app > > 3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file. > > 4. Build and run > > 5. Enjoy ! I was going to look into this method, but it's way above my head. Haha. I don't know a lot about code. I mean, I can follow instructions if listed, but I would need a step by step guide. I'll just hope for a fix.

kerem commented

Author

Owner

@Shimo commented on GitHub (Jan 7, 2026):

I just found a workaround. Let me explain

In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it :
1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps))

2. Clone the SpotiFLAC project and configure your environment to build and run the app

3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file.

4. Build and run

5. Enjoy !
I was going to look into this method, but it's way above my head. Haha. I don't know a lot about code. I mean, I can follow instructions if listed, but I would need a step by step guide. I'll just hope for a fix.

Debian based
sudo apt install -y golang-go nodejs npm build-essential git pkg-config libgtk-3-dev libwebkit2gtk-4.0-dev

Arch based
sudo pacman -S --needed go nodejs npm pnpm base-devel git pkgconf gtk3 webkit2gtk

Then
go install github.com/wailsapp/wails/v2/cmd/wails@latest

Change to the directory you want to store the build files in
git clone https://github.com/afkarxyz/SpotiFLAC
cd SpotiFLAC

Then open the file backend/spotify_metadata.go inside the folder you just cloned and edit the lines LePetit45 mentioned. If you need to convert your client ID and secret you can run this python command and it'll get it for you.

import base64
client_id = 'replace_with_your_client_id'
client_secret = 'replace_with_your_client_secret'
client_b64 = base64.b64encode(client_id.encode()).decode()
secret_b64 = base64.b64encode(client_secret.encode()).decode()
print("Client ID Base64:", client_b64)
print("Client Secret Base64:", secret_b64)

Then once you've replaced those entries with your api keys you can just run this from the terminal window you still have open.
wails build

If there are any errors it'll spit them out into terminal most likely it'll be missing dependancies I missed in my installs above if I did miss anything. Install them, and then try again. Otherwise you'll have a compiled executable in %/SpotiFLAC/build/bin/ % being wherever you cloned it to.

@Shimo commented on GitHub (Jan 7, 2026): > > ## I just found a workaround. Let me explain > > In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it : > > ``` > > 1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps)) > > > > 2. Clone the SpotiFLAC project and configure your environment to build and run the app > > > > 3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file. > > > > 4. Build and run > > > > 5. Enjoy ! > > ``` > > I was going to look into this method, but it's way above my head. Haha. I don't know a lot about code. I mean, I can follow instructions if listed, but I would need a step by step guide. I'll just hope for a fix. Debian based `sudo apt install -y golang-go nodejs npm build-essential git pkg-config libgtk-3-dev libwebkit2gtk-4.0-dev` Arch based `sudo pacman -S --needed go nodejs npm pnpm base-devel git pkgconf gtk3 webkit2gtk` Then `go install github.com/wailsapp/wails/v2/cmd/wails@latest` Change to the directory you want to store the build files in `git clone https://github.com/afkarxyz/SpotiFLAC` `cd SpotiFLAC` Then open the file backend/spotify_metadata.go inside the folder you just cloned and edit the lines LePetit45 mentioned. If you need to convert your client ID and secret you can run this python command and it'll get it for you. ``` import base64 client_id = 'replace_with_your_client_id' client_secret = 'replace_with_your_client_secret' client_b64 = base64.b64encode(client_id.encode()).decode() secret_b64 = base64.b64encode(client_secret.encode()).decode() print("Client ID Base64:", client_b64) print("Client Secret Base64:", secret_b64) ``` Then once you've replaced those entries with your api keys you can just run this from the terminal window you still have open. `wails build` If there are any errors it'll spit them out into terminal most likely it'll be missing dependancies I missed in my installs above if I did miss anything. Install them, and then try again. Otherwise you'll have a compiled executable in %/SpotiFLAC/build/bin/ % being wherever you cloned it to.

kerem commented

Author

Owner

@Shimo commented on GitHub (Jan 7, 2026):

Just to clarify to anyone who does use this "workaround" - your Spotify account will be banned, it's an eventuality. If you go this route, it's best to use a burner account's credentials.

Oof. Yeah, I don't want to risk that. Hope another solution can be found. If not, it was fun while it lasted.

I mean... As long as you're not going nuts with it or share it around, it'll just look like normal API traffic. Looks like they shut down creating api keys for now though. I've had premium for a long time and actually pull in my stats all the time so I already had an api key.

@Shimo commented on GitHub (Jan 7, 2026): > > Just to clarify to anyone who does use this "workaround" - your Spotify account will be banned, it's an eventuality. If you go this route, it's best to use a burner account's credentials. > > Oof. Yeah, I don't want to risk that. Hope another solution can be found. If not, it was fun while it lasted. I mean... As long as you're not going nuts with it or share it around, it'll just look like normal API traffic. Looks like they shut down creating api keys for now though. I've had premium for a long time and actually pull in my stats all the time so I already had an api key.

kerem commented

Author

Owner

@Silvergish commented on GitHub (Jan 7, 2026):

I just found a workaround. Let me explain

In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it :
1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps))

2. Clone the SpotiFLAC project and configure your environment to build and run the app

3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file.

4. Build and run

5. Enjoy !
I was going to look into this method, but it's way above my head. Haha. I don't know a lot about code. I mean, I can follow instructions if listed, but I would need a step by step guide. I'll just hope for a fix.
Debian based sudo apt install -y golang-go nodejs npm build-essential git pkg-config libgtk-3-dev libwebkit2gtk-4.0-dev

Arch based sudo pacman -S --needed go nodejs npm pnpm base-devel git pkgconf gtk3 webkit2gtk

Then go install github.com/wailsapp/wails/v2/cmd/wails@latest

Change to the directory you want to store the build files in git clone https://github.com/afkarxyz/SpotiFLAC cd SpotiFLAC

Then open the file backend/spotify_metadata.go inside the folder you just cloned and edit the lines LePetit45 mentioned. If you need to convert your client ID and secret you can run this python command and it'll get it for you.
import base64
client_id = 'replace_with_your_client_id'
client_secret = 'replace_with_your_client_secret'
client_b64 = base64.b64encode(client_id.encode()).decode()
secret_b64 = base64.b64encode(client_secret.encode()).decode()
print("Client ID Base64:", client_b64)
print("Client Secret Base64:", secret_b64)
Then once you've replaced those entries with your api keys you can just run this from the terminal window you still have open. wails build

If there are any errors it'll spit them out into terminal most likely it'll be missing dependancies I missed in my installs above if I did miss anything. Install them, and then try again. Otherwise you'll have a compiled executable in %/SpotiFLAC/build/bin/ % being wherever you cloned it to.

Thank you so much for the instructions! Will these instructions for macOS in Terminal?

@Silvergish commented on GitHub (Jan 7, 2026): > > > ## I just found a workaround. Let me explain > > > In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it : > > > ``` > > > 1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps)) > > > > > > 2. Clone the SpotiFLAC project and configure your environment to build and run the app > > > > > > 3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file. > > > > > > 4. Build and run > > > > > > 5. Enjoy ! > > > ``` > > > > > > I was going to look into this method, but it's way above my head. Haha. I don't know a lot about code. I mean, I can follow instructions if listed, but I would need a step by step guide. I'll just hope for a fix. > > Debian based `sudo apt install -y golang-go nodejs npm build-essential git pkg-config libgtk-3-dev libwebkit2gtk-4.0-dev` > > Arch based `sudo pacman -S --needed go nodejs npm pnpm base-devel git pkgconf gtk3 webkit2gtk` > > Then `go install github.com/wailsapp/wails/v2/cmd/wails@latest` > > Change to the directory you want to store the build files in `git clone https://github.com/afkarxyz/SpotiFLAC` `cd SpotiFLAC` > > Then open the file backend/spotify_metadata.go inside the folder you just cloned and edit the lines LePetit45 mentioned. If you need to convert your client ID and secret you can run this python command and it'll get it for you. > > ``` > import base64 > client_id = 'replace_with_your_client_id' > client_secret = 'replace_with_your_client_secret' > client_b64 = base64.b64encode(client_id.encode()).decode() > secret_b64 = base64.b64encode(client_secret.encode()).decode() > print("Client ID Base64:", client_b64) > print("Client Secret Base64:", secret_b64) > ``` > > Then once you've replaced those entries with your api keys you can just run this from the terminal window you still have open. `wails build` > > If there are any errors it'll spit them out into terminal most likely it'll be missing dependancies I missed in my installs above if I did miss anything. Install them, and then try again. Otherwise you'll have a compiled executable in %/SpotiFLAC/build/bin/ % being wherever you cloned it to. Thank you so much for the instructions! Will these instructions for macOS in Terminal?

kerem commented

Author

Owner

@alexthelion335 commented on GitHub (Jan 7, 2026):

I just found a workaround. Let me explain

In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it :
1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps))

2. Clone the SpotiFLAC project and configure your environment to build and run the app

3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file.

4. Build and run

5. Enjoy !

I am unable to create a new app in the developer portal, is this because Spotify is doing updates?

@alexthelion335 commented on GitHub (Jan 7, 2026): > ## I just found a workaround. Let me explain > > In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it : > > 1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps)) > > 2. Clone the SpotiFLAC project and configure your environment to build and run the app > > 3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file. > > 4. Build and run > > 5. Enjoy ! <img width="2553" height="1261" alt="Image" src="https://github.com/user-attachments/assets/42ede6dc-105a-4e2e-8fc3-1023a483a098" /> I am unable to create a new app in the developer portal, is this because Spotify is doing updates?

kerem commented

Author

Owner

@Silvergish commented on GitHub (Jan 8, 2026):

I just found a workaround. Let me explain

In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it :
1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps))

2. Clone the SpotiFLAC project and configure your environment to build and run the app

3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file.

4. Build and run

5. Enjoy !
I am unable to create a new app in the developer portal, is this because Spotify is doing updates?

I'm assuming they are doing something behind the scenes due to that scraping incident.

@Silvergish commented on GitHub (Jan 8, 2026): > > ## I just found a workaround. Let me explain > > > > In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it : > > > > 1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps)) > > > > 2. Clone the SpotiFLAC project and configure your environment to build and run the app > > > > 3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file. > > > > 4. Build and run > > > > 5. Enjoy ! > > <img width="2553" height="1261" alt="Image" src="https://github.com/user-attachments/assets/42ede6dc-105a-4e2e-8fc3-1023a483a098" /> > > I am unable to create a new app in the developer portal, is this because Spotify is doing updates? I'm assuming they are doing something behind the scenes due to that scraping incident.

kerem commented

Author

Owner

@B00-KER commented on GitHub (Jan 8, 2026):

Same error:
[08:29:11] [info] fetching track metadata...
[08:29:11] [debug] url: https://open.spotify.com/track/6cu0zwiwvtenmwpsjvhm93?si=00278ce240a3450d
[08:34:09] [error] fetch failed: failed to fetch metadata
[08:34:09] [error] failed to fetch metadata

@B00-KER commented on GitHub (Jan 8, 2026): Same error: [08:29:11] [info] fetching track metadata... [08:29:11] [debug] url: https://open.spotify.com/track/6cu0zwiwvtenmwpsjvhm93?si=00278ce240a3450d [08:34:09] [error] fetch failed: failed to fetch metadata [08:34:09] [error] failed to fetch metadata

kerem commented

Author

Owner

@talhoid commented on GitHub (Jan 8, 2026):

I can confirm that the client id and the client secret are now stale. They've also been used on almost every single spotify scraper that exists, so its no surprise they stopped working. You can't make any new applications on the spotify application dashboard right now. I have an application that I made however, so if anyone wants to use them you can dm me on discord at talhoid. I'm not going to post them here in fear of my account getting taken down.
Do not get mad at SpotiFLAC. It is not a fault of the application.

@talhoid commented on GitHub (Jan 8, 2026): I can confirm that the client id and the client secret are now stale. They've also been used on almost every single spotify scraper that exists, so its no surprise they stopped working. You can't make any new applications on the spotify application dashboard right now. I have an application that I made however, so if anyone wants to use them you can dm me on discord at `talhoid`. I'm not going to post them here in fear of my account getting taken down. Do not get mad at SpotiFLAC. It is not a fault of the application.

kerem commented

Author

Owner

@Silvergish commented on GitHub (Jan 8, 2026):

I can confirm that the client id and the client secret are now stale. They've also been used on almost every single spotify scraper that exists, so its no surprise they stopped working. You can't make any new applications on the spotify application dashboard right now. I have an application that I made however, so if anyone wants to use them you can dm me on discord at talhoid. I'm not going to post them here in fear of my account getting taken down. Do not get mad at SpotiFLAC. It is not a fault of the application.

Sent a friend request on Discord.

@Silvergish commented on GitHub (Jan 8, 2026): > I can confirm that the client id and the client secret are now stale. They've also been used on almost every single spotify scraper that exists, so its no surprise they stopped working. You can't make any new applications on the spotify application dashboard right now. I have an application that I made however, so if anyone wants to use them you can dm me on discord at `talhoid`. I'm not going to post them here in fear of my account getting taken down. Do not get mad at SpotiFLAC. It is not a fault of the application. Sent a friend request on Discord.

kerem commented

Author

Owner

@Shimo commented on GitHub (Jan 8, 2026):

I just found a workaround. Let me explain

In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it :
1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps))

2. Clone the SpotiFLAC project and configure your environment to build and run the app

3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file.

4. Build and run

5. Enjoy !
I was going to look into this method, but it's way above my head. Haha. I don't know a lot about code. I mean, I can follow instructions if listed, but I would need a step by step guide. I'll just hope for a fix.
Debian based sudo apt install -y golang-go nodejs npm build-essential git pkg-config libgtk-3-dev libwebkit2gtk-4.0-dev
Arch based sudo pacman -S --needed go nodejs npm pnpm base-devel git pkgconf gtk3 webkit2gtk
Then go install github.com/wailsapp/wails/v2/cmd/wails@latest
Change to the directory you want to store the build files in git clone https://github.com/afkarxyz/SpotiFLAC cd SpotiFLAC
Then open the file backend/spotify_metadata.go inside the folder you just cloned and edit the lines LePetit45 mentioned. If you need to convert your client ID and secret you can run this python command and it'll get it for you.
import base64
client_id = 'replace_with_your_client_id'
client_secret = 'replace_with_your_client_secret'
client_b64 = base64.b64encode(client_id.encode()).decode()
secret_b64 = base64.b64encode(client_secret.encode()).decode()
print("Client ID Base64:", client_b64)
print("Client Secret Base64:", secret_b64)
Then once you've replaced those entries with your api keys you can just run this from the terminal window you still have open. wails build
If there are any errors it'll spit them out into terminal most likely it'll be missing dependancies I missed in my installs above if I did miss anything. Install them, and then try again. Otherwise you'll have a compiled executable in %/SpotiFLAC/build/bin/ % being wherever you cloned it to.
Thank you so much for the instructions! Will these instructions for macOS in Terminal?

It should. I don't have too much experience with macOS though, but theoretically it should work just need to install the dependencies from wherever OSX gets those from. From what I understand it's homebrew? https://brew.sh/
And a quick search, so take it with a grain of salt, suggests that instead of build-essential you'll need xcode-select for compiling. So try these and let folks know if it works.

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
xcode-select --install
brew install go node git pkg-config gtk+3 webkit2gtk
And then just pick up from the git clone part of the previous steps.

If not you can always spin up a VM for it or a docker container running ubuntu or something. From what I can see VirtualBox works on OSX without any struggle and it can spin up an Ubuntu VM really easily. And then just share a folder between your OSX host and the Ubuntu guest. https://medium.com/macoclock/share-folder-between-macos-and-ubuntu-4ce84fb5c1ad

@Shimo commented on GitHub (Jan 8, 2026): > > > > ## I just found a workaround. Let me explain > > > > In SpotiFLAC, the app use default credentials for Spotify API requests. But, the account used may be banned or deactivated. So, if you want to use the app, you need to insert YOUR credentials. This is the way to do it : > > > > ``` > > > > 1. Get your client_id and secret_id from the spotify api dashboard ([Some documentation here](https://developer.spotify.com/documentation/web-api/concepts/apps)) > > > > > > > > 2. Clone the SpotiFLAC project and configure your environment to build and run the app > > > > > > > > 3. Change the client_id and secret_id variable, available in the `backend/spotify_metadata.go`, line 50 and 56. Don't forget to encode your credentials in base64 before insert to the file. > > > > > > > > 4. Build and run > > > > > > > > 5. Enjoy ! > > > > ``` > > > > > > > > > I was going to look into this method, but it's way above my head. Haha. I don't know a lot about code. I mean, I can follow instructions if listed, but I would need a step by step guide. I'll just hope for a fix. > > > > > > Debian based `sudo apt install -y golang-go nodejs npm build-essential git pkg-config libgtk-3-dev libwebkit2gtk-4.0-dev` > > Arch based `sudo pacman -S --needed go nodejs npm pnpm base-devel git pkgconf gtk3 webkit2gtk` > > Then `go install github.com/wailsapp/wails/v2/cmd/wails@latest` > > Change to the directory you want to store the build files in `git clone https://github.com/afkarxyz/SpotiFLAC` `cd SpotiFLAC` > > Then open the file backend/spotify_metadata.go inside the folder you just cloned and edit the lines LePetit45 mentioned. If you need to convert your client ID and secret you can run this python command and it'll get it for you. > > ``` > > import base64 > > client_id = 'replace_with_your_client_id' > > client_secret = 'replace_with_your_client_secret' > > client_b64 = base64.b64encode(client_id.encode()).decode() > > secret_b64 = base64.b64encode(client_secret.encode()).decode() > > print("Client ID Base64:", client_b64) > > print("Client Secret Base64:", secret_b64) > > ``` > > > > > > > > > > > > > > > > > > > > > > > > Then once you've replaced those entries with your api keys you can just run this from the terminal window you still have open. `wails build` > > If there are any errors it'll spit them out into terminal most likely it'll be missing dependancies I missed in my installs above if I did miss anything. Install them, and then try again. Otherwise you'll have a compiled executable in %/SpotiFLAC/build/bin/ % being wherever you cloned it to. > > Thank you so much for the instructions! Will these instructions for macOS in Terminal? It should. I don't have too much experience with macOS though, but theoretically it should work just need to install the dependencies from wherever OSX gets those from. From what I understand it's homebrew? https://brew.sh/ And a quick search, so take it with a grain of salt, suggests that instead of build-essential you'll need xcode-select for compiling. So try these and let folks know if it works. `/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"` `xcode-select --install` `brew install go node git pkg-config gtk+3 webkit2gtk` And then just pick up from the git clone part of the previous steps. If not you can always spin up a VM for it or a docker container running ubuntu or something. From what I can see VirtualBox works on OSX without any struggle and it can spin up an Ubuntu VM really easily. And then just share a folder between your OSX host and the Ubuntu guest. https://medium.com/macoclock/share-folder-between-macos-and-ubuntu-4ce84fb5c1ad

kerem commented

Author

Owner

@Silvergish commented on GitHub (Jan 8, 2026):

it should work just need to install the dependencies from wherever OSX gets those from. From what I understand it's homebrew? https://brew.sh/ And a quick search, so take it with a grain of salt, suggests that instead of build-essential you'll need xcode-select for compiling. So try these and let folks know if it works.

``

I was able to build the app, but I have no way to find my client id and the client secret.

@Silvergish commented on GitHub (Jan 8, 2026): > it should work just need to install the dependencies from wherever OSX gets those from. From what I understand it's homebrew? https://brew.sh/ And a quick search, so take it with a grain of salt, suggests that instead of build-essential you'll need xcode-select for compiling. So try these and let folks know if it works. > > `` I was able to build the app, but I have no way to find my client id and the client secret.

kerem commented

Author

Owner

@Ramog commented on GitHub (Jan 8, 2026):

it should work just need to install the dependencies from wherever OSX gets those from. From what I understand it's homebrew? https://brew.sh/ And a quick search, so take it with a grain of salt, suggests that instead of build-essential you'll need xcode-select for compiling. So try these and let folks know if it works.
``

I was able to build the app, but I have no way to find my client id and the client secret.

its not about your client really, its about a api key
and being that spotify apperently locked down creation of new applications (which is how you get the API keys) you probably won't be able to get it to work currently except if you already have an app registered

@Ramog commented on GitHub (Jan 8, 2026): > > it should work just need to install the dependencies from wherever OSX gets those from. From what I understand it's homebrew? https://brew.sh/ And a quick search, so take it with a grain of salt, suggests that instead of build-essential you'll need xcode-select for compiling. So try these and let folks know if it works. > > `` > > I was able to build the app, but I have no way to find my client id and the client secret. its not about your client really, its about a api key and being that spotify apperently locked down creation of new applications (which is how you get the API keys) you probably won't be able to get it to work currently except if you already have an app registered

kerem commented

Author

Owner

@Silvergish commented on GitHub (Jan 8, 2026):

it should work just need to install the dependencies from wherever OSX gets those from. From what I understand it's homebrew? https://brew.sh/ And a quick search, so take it with a grain of salt, suggests that instead of build-essential you'll need xcode-select for compiling. So try these and let folks know if it works.
``

I was able to build the app, but I have no way to find my client id and the client secret.

its not about your client really, its about a api key and being that spotify apperently locked down creation of new applications (which is how you get the API keys) you probably won't be able to get it to work currently except if you already have an app registered

Ahh. Ok. Thanks for the explanation. So since I don't have any Spotify app, I'm dead in the water. Haha. That makes sense. I'm trying to learn as I go.

@Silvergish commented on GitHub (Jan 8, 2026): > > > it should work just need to install the dependencies from wherever OSX gets those from. From what I understand it's homebrew? https://brew.sh/ And a quick search, so take it with a grain of salt, suggests that instead of build-essential you'll need xcode-select for compiling. So try these and let folks know if it works. > > > `` > > > > > > I was able to build the app, but I have no way to find my client id and the client secret. > > its not about your client really, its about a api key and being that spotify apperently locked down creation of new applications (which is how you get the API keys) you probably won't be able to get it to work currently except if you already have an app registered Ahh. Ok. Thanks for the explanation. So since I don't have any Spotify app, I'm dead in the water. Haha. That makes sense. I'm trying to learn as I go.

kerem commented

Author

Owner

@lukas-hablitzel commented on GitHub (Jan 9, 2026):

I can confirm that the client id and the client secret are now stale. They've also been used on almost every single spotify scraper that exists, so its no surprise they stopped working. You can't make any new applications on the spotify application dashboard right now. I have an application that I made however, so if anyone wants to use them you can dm me on discord at talhoid. I'm not going to post them here in fear of my account getting taken down. Do not get mad at SpotiFLAC. It is not a fault of the application.

Also sent you a friend request, thanks so much!

@lukas-hablitzel commented on GitHub (Jan 9, 2026): > I can confirm that the client id and the client secret are now stale. They've also been used on almost every single spotify scraper that exists, so its no surprise they stopped working. You can't make any new applications on the spotify application dashboard right now. I have an application that I made however, so if anyone wants to use them you can dm me on discord at `talhoid`. I'm not going to post them here in fear of my account getting taken down. Do not get mad at SpotiFLAC. It is not a fault of the application. Also sent you a friend request, thanks so much!

kerem commented

Author

Owner

@sergiocastrovale commented on GitHub (Jan 11, 2026):

So, let me get this right.

SpotiFLAC uses an account, and it gets banned.

... and the proposed solution is to use OUR OWN account? Isn't the obvious outcome to have it banned as well?

@sergiocastrovale commented on GitHub (Jan 11, 2026): So, let me get this right. SpotiFLAC uses an account, and it gets banned. ... and the proposed solution is to use OUR OWN account? Isn't the obvious outcome to have it banned as well?

kerem commented