SpotifyXP stuck on "creating api..."

[HIXOXIH]

Just like the first time I used SpotifyXP, after the installation process, nothing else happens. It doesn't create the icon on the desktop and the login screen doesn't appear. But then I used the same method I used the previous time to get it running (--setup-complete --debug). Then it opens but gets stuck on the "creating api..." screen.
I do what the message says for the new login method (I open Spotify on my smartphone and tap on devices) but nothing happens and SpotifyXP doesn't appear on Spotify devices. Help me!

Note:I,m using SpotifyXP 2.0.3 and my account is premium

[werwolf2303]

Please give me the full system specs including language and username. This way I can check if the icon problem has anything to do with special characters.

Does your network allow local network connections?
Are the pc and the phone on the same network?

[werwolf2303]

I will investigate the creating api issue when I finished the switch to Android

[HIXOXIH]

My language is Brazilian Portuguese. My Spotify username is h4v0ck. My PC and smartphone are on the same network and I could find SPOTIFYXP on Spotify on my phone before.

[werwolf2303]

When did it stop working?

[HIXOXIH]

It stopped when you said that the project had died due to a login modification made by the Spotify team. But I did the new method that you discovered and that brought the project back to life.It turns out that I'm not able to get out of the "creating api..." screen even after following the steps to log in. In fact, I don't think I'll ever be able to because of this new version that I downloaded at your request (2.0.3) The login screen did not appear for me. Therefore, it cannot appear on my smartphone's Spotify devices because for this to happen, I must first log in to SpotifyXP using the same account that I am using on Spotify. Only after this will SpotifyXP appear in the list of Spotify devices on my cell phone. Em qui, 26 de set de 2024 11:33, werwolf2303 ***@***.***> escreveu:

…

When did it stop working? — Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BIXONPWGVGJPEMMGUH4KYRDZYQLKVAVCNFSM6AAAAABOTBWYFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGE2TAMRRHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[werwolf2303]

Hmm. I see what I can do about that tomorrow

[werwolf2303]

I don't know why it doesn't work. But I will continue investigating

[HIXOXIH]

I imagine it's not appearing on Spotify devices on my smartphone because I would need to log into SpotifyXP and then it would appear. It would be like wanting a normal Spotify for desktop that has just been installed and that has not yet entered the account credentials, to appear on the mobile version devices. Because for this to happen, you need to not only be on the same network but also be using the same account on both.

[werwolf2303]

I use the Spotify connect protocol. It's normally for embedded devices such as Sonos speakers. It broadcasts itself onto the network. It doesn't care if the device itself is logged in

[HIXOXIH]

Well... then I have no idea why it doesn't work. Do you have any more recent version I could try?

[Jri-creator]

I wonder... What happens if somebody tries to pair with Spotify-compatible devices, such as Sonos Speakers, with a free plan. Would it produce the same result [Upgrade to Premium] or will it be different? If it's different, is there a way to mock the device with SpotifyXP so that it works on the free plan?

…

On October 1, 2024 9:23:51 PM EDT, HIXOXIH ***@***.***> wrote: Well... then I have no idea why it doesn't work. Do you have any more recent version I could try? -- Reply to this email directly or view it on GitHub: #56 (comment) You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

[werwolf2303]

You can actually pair some speakers with a free plan but only the speakers that have a newer Spotify library version

[HIXOXIH]

My account is premium.

[werwolf2303]

The thing is it worked when I implemented it. so I don't know what happened

[HIXOXIH]

😔😔😔