Floating Control Bar extending out of bounds on 1.82.x.x

[Sonicx9876]

Is there any way to fix this

[rlaphoenix]

Hi, any chance you could tell me what Spotify version you are on from the ⋯ button, File, Help, and click the Copy to Clipboard button.
What method did you use to install, and does this only happen when you enlarge the album cover?

[Sonicx9876]

Hi, any chance you could tell me what Spotify version you are on from the ⋯ button, File, Help, and click the Copy to Clipboard button. What method did you use to install, and does this only happen when you enlarge the album cover?

Spotify for Windows
1.1.82.758.g8b7b66c7
that was with the album cover enlarged when it is not it just goes on top of the title. I installed it from the github and used powershell.

[rlaphoenix]

It looks like 1.1.82.x might not be supported yet. It seems 1.1.82.x only just recently came out as well. 1.1.79.x is supported, and 1.1.80.x might also be supported. 1.1.81.x is likely not supported, nor is 1.1.82.x.

It seems even Spicetify-cli has yet to receive full support for 1.1.81.x let alone 1.1.82.x. You may want to downgrade Spotify to 1.1.79.x or 1.1.80.x until Spicetify-cli gets full support for newer versions. You will want to block Spotify updates once you downgrade (before opening Spotify after installation).

You can block updates by simply running the following command after downgrading:

icacls "C:\Users\$($env:UserName)\AppData\Local\Spotify\Update" /deny "$($env:UserName):W"

And for reference, to unblock, you run:

icacls "C:\Users\$($env:UserName)\AppData\Local\Spotify\Update" /grant "$($env:UserName):W"

[rlaphoenix]

I cannot replicate this on Spotify for Windows 1.1.81.604.gccacfc8c (slightly older ver. than you) no matter what combination or setup I do with spicetify-cli. It may have broken support somewhere after 81.604.

1. Try downgrade to this version using this archive.
2. Ensure you are on Spicetify-cli v2.9.5 (latest), though as old as v2.9.2 works to some degree.
3. spicetify backup apply
4. Spotify should open and hopefully it looks correct.

I'm also aware 1.1.82 is where the issue arises, but at least we can get as far as 1.1.81 without any noticeable errors.
I also cannot find any installer for 1.1.82 from a reputable place so I cannot yet debug the issue.