Allow "spicetify auto" to forward arguments/URIs to Spotify

[riukii]

📝 Provide a description of the new feature

Currently, spicetify auto does not forward arguments to the Spotify instance it launches. This breaks Linux desktop integration because passing %U or --uri= arguments (for spotify:// links) via .desktop files is ignored by the auto command.

Could you please add argument forwarding to spicetify auto so it passes trailing arguments directly to the spawned Spotify process?

➕ Additional Information

No response

[rxri]

That's what spotify_launch_options is for

[riukii]

I don't think that passing the url in this way really works, but I still managed to solve my problem by starting Spotify with a script instead. For everyone that might need it:

#!/bin/bash

URI="$1"

if pgrep -x "spotify" > /dev/null; then
    if [ -n "$URI" ]; then
        /usr/bin/spotify --uri="$URI" > /dev/null 2>&1 &
    else
        /usr/bin/spotify > /dev/null 2>&1 &
    fi
else
    spicetify auto

    if [ -n "$URI" ]; then
        sleep 2
        /usr/bin/spotify --uri="$URI" > /dev/null 2>&1 &
    fi
fi

Then just set the Exec in the Spotify's .desktop to this script name with %u at the end, for example like path/to/spicetify-script %u. (If you are on kde you might want to do kbuildsycoca6 in the terminal after doing all of this to refresh the cache).

[rxri]

Any launch option there will be passed to spotify when spicetify auto is used

[riukii]

Yeah but I need to pass a dynamic argument, even if I write in spicetify configs %u as launch arguments so that it'll be passed to Spotify, it will pass an empty argument unless in the Spotify's .desktop I also specify something like spicetify auto %u. But this approach I'm not sure is working, maybe I'm doing something wrong tho.

[rxri]

You can always modify the config at any time programmatically and it will be read freshly on every command usage

[riukii]

Modifying the config file programmatically doesn't work for system-level deep-linking.
When a user clicks a spotify:// link in a browser or app (e.g. Spotify's account in a Discord's user profile or a song link in some browser), the OS immediately fires the desktop launcher with the URL as a dynamic argument (e.g., spicetify auto spotify:track:xxxx). There is no script or hook in between that can intercept that click, open the config-xpui.ini, rewrite the line, save it, and then let the command run.
Operating systems handle protocol layouts via CLI arguments (%u on Linux/macOS, %1 on Windows). If spicetify auto acts as the wrapper/launcher for Spotify, it has to accept and forward trailing CLI arguments, otherwise deep-linking is completely broken when using it.