Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Something went wrong" error when launching spotify #3086

Closed
2 tasks done
zjeffer opened this issue Jun 28, 2024 · 4 comments
Closed
2 tasks done

"Something went wrong" error when launching spotify #3086

zjeffer opened this issue Jun 28, 2024 · 4 comments
Labels

Comments

@zjeffer
Copy link

zjeffer commented Jun 28, 2024

πŸ” Have you checked Spicetify.app page for your issue?

  • I have checked the FAQ

πŸ” Is there already an issue for your problem?

  • I have checked older issues, open and closed

β„Ή Environment / Computer Info

- Spotify version: spicetify-cli-git 2.36.11.r5.ge23e0f2-1
- Spicetify version: spotify 1:1.2.40.599-1

Installed with paru from the AUR.

πŸ“ Description

Launching spicetify gives the below "Something went wrong" error.

Things I tried:

  • spicetify restore backup
  • spicetify update and spicetify upgrade (both failed because I installed it from AUR so it didn't have permissions)
  • spicetify backup apply
  • spicetify clear

Spotify works fine after restoring.

πŸ“Έ Screenshots

image

@zjeffer zjeffer added the πŸ› bug Something isn't working label Jun 28, 2024
@rxri
Copy link
Member

rxri commented Jun 28, 2024

v2.36.11 is not latest version of spicetify. v2.36.13 fixed this issue for Spotify 1.2.40

@rxri rxri closed this as not planned Won't fix, can't repro, duplicate, stale Jun 28, 2024
@zjeffer
Copy link
Author

zjeffer commented Jun 28, 2024

Ah, something must have gone wrong with paru or the AUR package's PKGBUILD. I tried upgrading and reinstalling spicetify multiple times and each time it upgraded to 2.36.11, so I assumed I was on the latest version.

I deleted the ~/.cache/paru/clone/spicetify-cli-git folder and upgraded it again through paru, now it works fine.

Thanks for the quick support!

@rxri
Copy link
Member

rxri commented Jun 28, 2024

I recommend using spicetify-cli and not spicetify-cli-git in the prod. Git repo can always have something broken and is not really intended for daily usage, but it's up to you ofc. spicetify-cli is updated as soon as we make a release because of hooked up update process

@zjeffer
Copy link
Author

zjeffer commented Jun 28, 2024

That's ok, I like using git versions of packages so I can help investigate and fix potential issues with the repo before a release is made ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants