Skip to content

spicetify auto is not useful in its current stateΒ #2204

Description

@SteffanDonal

πŸ” 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: 1.2.7.1277.g2b3ce637
- Spicetify version: v2.16.2

πŸ“ Description

The FAQ mentions:

After Spotify's update, running spicetify apply or spicetify update breaks Spotify.

After any Spotify update, always run spicetify backup apply.
Optionally, make Spotify shortcut to run spicetify auto (instead of direct path to spotify executable), so that Spicetify can backup and apply, when it needs to, then launch Spotify automatically.

It may be the case that Spicetify is not supporting this new Spotify update yet. In that case, check our issue tracker.

However, this command does not launch Spotify as expected.
It will update and restart, if Spotify is already open. This doesn't make much sense given the suggestion that spicetify auto is a silver bullet for the "how do I set and forget Spicetify so I don't have to interact with a terminal" problem.

I did a little digging and saw a fix for an unrelated issue made last year as the cause of this command becoming much less useful. It should be possible to do both; not launch Spotify when calling spicetify backup apply, but do launch it when calling spicetify auto.

πŸ“Έ Screenshots

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions