password is not set and credentials are not in cache

[boris19]

mopidy-Spotify worked normally for me until Spotify itself changed my login data. since then I've been struggling with the logo in moped: GStreamer error: Could not get/set settings from/on resource. then I tried everything like refresh token, I reinstalled mopeds more things. I found the command option here in the bugs:
gst-launch-1.0 spotifyaudiosrc username=$USERNAME password=$PASSWORD track=spotify:track:3i3P1mGpV9eRlfKccjDjwi ! oggdemux ! vorbisdec ! audioconvert ! autoaudiosink

who writes me this message:

Setting pipeline to PAUSED ... Pipeline is PREROLLING ... ERROR: from element /GstPipeline:pipeline0/GstSpotifyAudioSrc:spotifyaudiosrc0: Could not get/set settings from/on resource. Additional debug info: audio/spotify/src/spotifyaudiosrc/imp.rs(239): <gstspotify::spotifyaudiosrc::imp::SpotifyAudioSrc as gstreamer_base::subclass::push_src::PushSrcImpl>::create (): /GstPipeline:pipeline0/GstSpotifyAudioSrc:spotifyaudiosrc0: password is not set and credentials are not in cache ERROR: pipeline doesn't want to preroll. WARNING: from element /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0: Failed to connect: Connection refused Additional debug info: ../ext/pulse/pulsesink.c(616): gst_pulseringbuffer_open_device (): /GstPulseSink:autoaudiosink0-actual-sink-pulse ERROR: from element /GstPipeline:pipeline0/GstSpotifyAudioSrc:spotifyaudiosrc0: Internal data stream error. Additional debug info: ../libs/gst/base/gstbasesrc.c(3132): gst_base_src_loop (): /GstPipeline:pipeline0/GstSpotifyAudioSrc:spotifyaudiosrc0: streaming stopped, reason error (-5) ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... ERROR: from element /GstPipeline:pipeline0/GstOggDemux:oggdemux0: Could not demultiplex stream. Additional debug info: ../ext/ogg/gstoggdemux.c(4775): gst_ogg_demux_send_event (): /GstPipeline:pipeline0/GstOggDemux:oggdemux0: EOS before finding a chain ERROR: pipeline doesn't want to preroll. Freeing pipeline ...

some experience please.

[kingosticks]

I'm not sure I totally understand what has happened to you here (what is moped??) but there is an issue right now which essentially means username and password login is broken (mentioned at #110 (comment) However, I don't think that is your issue here. I would guess you didn't define $USERNAME? But even if you did, it would no longer work in the wake of Spotify disabling username+password login.

[kingosticks]

No response and we already have issues tracking the auth changes.