search

SpotX-Official / SpotX-Bash

SpotX Mac and Linux adblocker for the Spotify desktop client, in Bash
MIT License
2.19k stars 75 forks source link

[Linux] SpotX-Bash currently broken with v1.2.48.405 #64

Open fegauthier opened 19 hours ago

fegauthier commented 19 hours ago

๐Ÿง Have you fully read the README and viewed similar issues?

ะกountry of your account

Canada

What is your Spotify Plan?

Free

Do you have Spicetify installed?

No

โ„น Computer information

- Spotify version: 1.2.48.405
- OS: ZorinOS 17.2
- Shell: ZSH

๐Ÿ“ Description

  1. Since this morning, Spotify doesn't work with SpotX. It works without

image

I uninstall SpotX, and Spotify works when uninstalled.

๐Ÿ–ฅ๏ธ Terminal Input/Output

bash <(curl -sSL https://spotx-official.github.io/run.sh)

โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ•— โ–ˆโ–ˆโ–ˆโ•— โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ•— โ–ˆโ•— โ–ˆโ–ˆโ–ˆโ•— โ–ˆโ–ˆโ•— โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ•— โ–ˆโ•— โ–ˆโ•”โ•โ•โ•โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ•โ–ˆโ•—โ•šโ•โ–ˆโ•”โ•โ•โ•šโ–ˆโ•—โ–ˆโ•”โ• โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ•โ•โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ•”โ•โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ•‘ โ•šโ–ˆโ•”โ•โ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ•”โ•โ–ˆโ–ˆโ–ˆโ–ˆโ•‘โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ–ˆโ•‘ โ•šโ•โ•โ–ˆโ•‘โ–ˆโ•”โ•โ• โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ•”โ–ˆโ•—โ•šโ•โ•โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ–ˆโ•‘โ•šโ•โ•โ–ˆโ•‘โ–ˆโ•”โ•โ–ˆโ•‘ โ–ˆโ–ˆโ–ˆโ–ˆโ•‘โ–ˆโ•‘ โ•šโ–ˆโ–ˆโ–ˆโ•”โ• โ–ˆโ•‘ โ–ˆโ•”โ• โ–ˆโ•— โ–ˆโ–ˆโ–ˆโ•”โ•โ–ˆโ•‘ โ–ˆโ•‘โ–ˆโ–ˆโ–ˆโ–ˆโ•‘โ–ˆโ•‘ โ–ˆโ•‘ โ•šโ•โ•โ•โ•โ•šโ• โ•šโ•โ•โ• โ•šโ• โ•šโ• โ•šโ• โ•šโ•โ•โ• โ•šโ• โ•šโ•โ•šโ•โ•โ•โ•โ•šโ• โ•šโ•

Searching for client directory...

Found client Directory: /usr/share/spotify

Latest supported version: 1.2.48.405 Detected client version: 1.2.48.405

โœ” Created backup โœ” Applied free-tier plan patches โœ” Enabled experimental features โœ” Finished

๐Ÿ“ธ Screenshots

No response

jetfir3 commented 14 hours ago

SpotX-Bash is currently only tested with v1.2.48.x on macOS -- which was released ~2 weeks ago. The Linux release of v1.2.48.x was made available only ~24hrs ago and may not be ready for SXB yet.

SXB will be updated later today for Spotify v1.2.49.x on macOS and then I'll take a look at 1.2.48.405 for Linux.

jetfir3 commented 12 hours ago
  1. Since this morning, Spotify doesn't work with SpotX. It works without ... I uninstall SpotX, and Spotify works when uninstalled.

I finally got around to checking today's 1.2.48.405 update on Linux and I can't replicate the issue you're seeing.

I'm wondering if it's a conflict with some previous app data?

Which version of Spotify was previously installed before upgrading to 1.2.48.405.. and was SpotX-Bash used on the previous version?

If you run the SpotX-Bash install and add the -c flag to clear cache.. any changes? 

bash <(curl -sSL https://spotx-official.github.io/run.sh) -c

If -c doesn't resolve it -- have you tried the FULL uninstall steps mentioned in the Troubleshooting Guide.. either the manual or automated script?

I'm curious what happens for you on a complete uninstall and fresh SpotX-Bash install -- ideally not launching STOCK Spotify prior to patching the client with SpotX-Bash.

fegauthier commented 10 hours ago

Even with

bash <(curl -sSL https://spotx-official.github.io/run.sh) -c

I had the same results.

I have the same results with uninstallify and reinstalling using the command below

`bash <(curl -sSL https://spotx-official.github.io/run.sh) -c

โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ•— โ–ˆโ–ˆโ–ˆโ•— โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ•— โ–ˆโ•— โ–ˆโ–ˆโ–ˆโ•— โ–ˆโ–ˆโ•— โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ•— โ–ˆโ•— โ–ˆโ•”โ•โ•โ•โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ•โ–ˆโ•—โ•šโ•โ–ˆโ•”โ•โ•โ•šโ–ˆโ•—โ–ˆโ•”โ• โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ•โ•โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ•”โ•โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ•‘ โ•šโ–ˆโ•”โ•โ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ•”โ•โ–ˆโ–ˆโ–ˆโ–ˆโ•‘โ–ˆโ–ˆโ–ˆโ–ˆโ•—โ–ˆโ–ˆโ–ˆโ–ˆโ•‘ โ•šโ•โ•โ–ˆโ•‘โ–ˆโ•”โ•โ• โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ•‘ โ–ˆโ•”โ–ˆโ•—โ•šโ•โ•โ–ˆโ•”โ•โ–ˆโ•—โ–ˆโ•”โ•โ–ˆโ•‘โ•šโ•โ•โ–ˆโ•‘โ–ˆโ•”โ•โ–ˆโ•‘ โ–ˆโ–ˆโ–ˆโ–ˆโ•‘โ–ˆโ•‘ โ•šโ–ˆโ–ˆโ–ˆโ•”โ• โ–ˆโ•‘ โ–ˆโ•”โ• โ–ˆโ•— โ–ˆโ–ˆโ–ˆโ•”โ•โ–ˆโ•‘ โ–ˆโ•‘โ–ˆโ–ˆโ–ˆโ–ˆโ•‘โ–ˆโ•‘ โ–ˆโ•‘ โ•šโ•โ•โ•โ•โ•šโ• โ•šโ•โ•โ• โ•šโ• โ•šโ• โ•šโ• โ•šโ•โ•โ• โ•šโ• โ•šโ•โ•šโ•โ•โ•โ•โ•šโ• โ•šโ•

Searching for client directory...

Warning: Client not found. Starting interactive mode...

Latest supported version: 1.2.49.439 Requested client version: 1.2.48.405

โœ” Started interactive mode [enter y/n]

Download & install client 1.2.48.405 deb pkg? y Clear client app cache? y Enable developer mode? y Hide non-music categories on home screen? y Set lyrics background color to black? y

############################################################################################################################################################################## 100.0% โœ” Downloaded and installing Spotify โœ” Installed in '/usr/share/spotify' โœ” Cleared app cache โœ” Created backup โœ” Applied free-tier plan patches โœ” Enabled developer mode โœ” Enabled experimental features โœ” Removed non-music categories on home screen โœ” Finished `

image

jetfir3 commented 9 hours ago

Even with

bash <(curl -sSL https://spotx-official.github.io/run.sh) -c

I had the same results.

I have the same results with uninstallify and reinstalling using the command below

When you ran uninstallify then SXB afterwards.. did you have to sign back into Spotify after it launched? Just want to confirm things were properly deleted since you didn't share the uninstallify output.

if you re-run SXB with the -e flag to disable all experimental settings, does anything change?

bash <(curl -sSL https://spotx-official.github.io/run.sh) -ef

this can help narrow down if there's some experimental setting being used that your account doesn't like for some reason. if using -e doesn't change anything then we at least know it's not an experimental setting... but I still have no ideas what could be happening at the moment and am still unable to replicate this behavior. Both upgrading from the previous 1.2.47.x build.. and fully uninstalling everything and running the exact commands you used result in a fully working Spotify on my Arch, Debian and Ubuntu installs.

fegauthier commented 8 hours ago

Spotify asked me to relogin yes. I tried with -ef but the result is the same. It's really weird.

fegauthier commented 8 hours ago

The issue seems to be about my network. If I enable a VPN, Spotify is working. If not, it doesnt work. Maybe my WAN IP was banned? I will take a look at my network.

jetfir3 commented 7 hours ago

Spotify asked me to relogin yes. I tried with -ef but the result is the same. It's really weird.

The issue seems to be about my network. If I enable a VPN, Spotify is working. If not, it doesnt work. Maybe my WAN IP was banned? I will take a look at my network.

Hmm.. it's even more strange because things seem to work with Spotify is NOT patched (right?) but breaks when patched with SXB. But... now it's fixed when VPN is used?!

I don't doubt this feedback.. Spotify can do some weird things.. but I can't recall ever coming across this exact error from any users.

If Spotify was broken, both with and without SXB, then it would make a little more sense. But with the following requiring a VPN to work:

bash <(curl -sSL https://spotx-official.github.io/run.sh)

and then the following allows it to work WITHOUT a VPN:

bash <(curl -sSL https://spotx-official.github.io/run.sh) --uninstall

... I'm quite confused.

Please keep me posted of any findings and , if possible, be as detailed as you can.. and maybe this can get sorted. I doubt your IP was BANNED by Spotify.. but there could be some sort of CDN issue or something.

amd64fox commented 7 hours ago

Perhaps the problem is related to this expenableBrotliCompressionViaCDN

or with any other, sometimes they use convoluted descriptions

I would just compare the exp, what is enabled/disabled in the native client and compare it with what is in SpotX

fegauthier commented 7 hours ago

Spotify asked me to relogin yes. I tried with -ef but the result is the same. It's really weird.

The issue seems to be about my network. If I enable a VPN, Spotify is working. If not, it doesnt work. Maybe my WAN IP was banned? I will take a look at my network.

Hmm.. it's even more strange because things seem to work with Spotify is NOT patched (right?) but breaks when patched with SXB. But... now it's fixed when VPN is used?!

I don't doubt this feedback.. Spotify can do some weird things.. but I can't recall ever coming across this exact error from any users.

If Spotify was broken, both with and without SXB, then it would make a little more sense. But with the following requiring a VPN to work:

bash <(curl -sSL https://spotx-official.github.io/run.sh)

and then the following allows it to work WITHOUT a VPN:

bash <(curl -sSL https://spotx-official.github.io/run.sh) --uninstall

... I'm quite confused.

Please keep me posted of any findings and , if possible, be as detailed as you can.. and maybe this can get sorted. I doubt your IP was BANNED by Spotify.. but there could be some sort of CDN issue or something.

  • is the VPN server you're testing with also in Canada.. or another region?
  • is your Spotify.com account set to Canada? https://www.spotify.com/account/profile/
  • you have no issues accessing Spotify.com and signing in (with VPN OFF)?
  • you have no issues accessing/using open.spotify.com web player (with VPN OFF)?

I'm pretty sure that the problem comes from my PC because on my laptop, it's working. I played with routing table this weekend. I probably messed with something. My laptop is using Zorin OS too and it's working. When I activate VPN on my PC. It plays with routing table. That's why it's working I guess.

jetfir3 commented 6 hours ago

Perhaps the problem is related to this expenableBrotliCompressionViaCDN

or with any other, sometimes they use convoluted descriptions

I would just compare the exp, what is enabled/disabled in the native client and compare it with what is in SpotX

As always, you've brought up some good ideas. Comparing remote config and experimental features between stock and patched will be easiest route (assuming it's config/exp issue and not another patch made by SXB).

I'm pretty sure that the problem comes from my PC because on my laptop, it's working. I played with routing table this weekend. I probably messed with something. My laptop is using Zorin OS too and it's working. When I activate VPN on my PC. It plays with routing table. That's why it's working I guess.

You previously mentioned that things WERE working with STOCK but WEREN'T working after SXB patched Spotify. Are you 1000% sure that is the case? As that specific variable changes what may be needed to sort this issue out.

If you turn OFF the VPN, exit Spotify and then run the SXB uninstall command, the home screen loads properly next time you launch Spotify?

bash <(curl -sSL https://spotx-official.github.io/run.sh) --uninstall

and then running the following causes the home screen to NOT load again?

bash <(curl -sSL https://spotx-official.github.io/run.sh)

If the --uninstall command DOES load the Spotify home screen properly, we need to debug your Spotify remote config values.. between stock/unpatched and after patching. I'll have to give you steps to gather these values on stock and patched.

If it DOESN'T load properly, then it would seem the issue is as you last described.. some network settings issue on your desktop.

amd64fox commented 6 hours ago

I played with routing table this weekend

in this case there is no point in testing anything, you need to bring the network to stock state