Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Plan
Premium
Country
Device
Xenia 14
Operating System
Linux
My Question or Issue
Hello!, thanks for the app in Linux!. I have question my self when it could implement the function Jam, it's only this.
Greetings.
Same here, Jam are a cool feature but we can't start one in Linux, this is real sad and we feel like second-class users while we are paying like the others !
Update to jam feature. I was able to start a jam, but was unable to join an existing jam.
When trying to join jam, app does receive something from opening the link (see below). But nothing beyond this.
02:19:10.843 D [f:764 ] ConnectManager cluster changed: reason DEVICES_DISAPPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:11.044 D [f:294 ] ConnectState cluster changed: reason DEVICES_DISAPPEARED
02:19:13.002 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:13.043 D [f:764 ] ConnectManager cluster changed: reason NEW_DEVICE_APPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:13.245 D [f:294 ] ConnectState cluster changed: reason NEW_DEVICE_APPEARED
02:19:15.387 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:15.393 D [f:764 ] ConnectManager cluster changed: reason DEVICES_DISAPPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:15.593 D [f:294 ] ConnectState cluster changed: reason DEVICES_DISAPPEARED
02:19:17.381 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:17.393 D [f:764 ] ConnectManager cluster changed: reason NEW_DEVICE_APPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:17.595 D [f:294 ] ConnectState cluster changed: reason NEW_DEVICE_APPEARED
02:19:20.108 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:20.143 D [f:764 ] ConnectManager cluster changed: reason DEVICES_DISAPPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:20.344 D [f:294 ] ConnectState cluster changed: reason DEVICES_DISAPPEARED
02:19:24.920 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:24.943 D [f:764 ] ConnectManager cluster changed: reason NEW_DEVICE_APPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:25.145 D [f:294 ] ConnectState cluster changed: reason NEW_DEVICE_APPEARED
02:19:25.718 I [f:202 ] ConcurrentCollector ran mark cycle for 16.012ms, total: 48.035ms.
02:19:32.994 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:33.043 D [f:764 ] ConnectManager cluster changed: reason DEVICES_DISAPPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:33.244 D [f:294 ] ConnectState cluster changed: reason DEVICES_DISAPPEARED
02:19:40.041 I [f:1598 ] No product state was retrieved, unable to update
Workaround: join jam on phone and swap active device to desktop.
Same problem here. Have tried both Snap and .deb versions of the spotify-client package under Linux mint. I can't see "nearby" jams on the same network, and when I click links to join a jam they're not recognised as Spotify URIs and they just open in Firefox and don't forward the link to the spotify client. Also tried Chromium browser with the same result.
Most spotify URLs you can open in the app from on the commandline as https $ spotify https://open.spotify.com/track/1QgLpUJsmrLG61KDVGT0Ux?si=82c8d692881a401d or the same with the spotify URL schema spotify spotify:track:1QgLpUJsmrLG61KDVGT0Ux However, neither of these methods work for jams using the spotify provided share links. Something is broken inside the linux client. The only workaround is to start the jams myself, since I can't join any.
I found a workaround for this issue...
Form the short URL spotify.link/ABABABABABAB use get the FULL URL (either from opening it in the browser or a using a service like spotify-uri-url-converter)
From the FULL URL: open.spotify.com/socialsession/ABC123ABC123ABC123ABC123
Now just use the URI: spotify:socialsession:ABC123ABC123ABC123ABC123
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…