<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Flic with Spotify Loses Authentication]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I recently set up my Flic Button to control music using the Spotify Web Connect integration (press=next, double=play/pause, hold=start playlist).</p>
<p dir="auto">It works great for a while, then continually stops working after a small period of time (&lt;4 hours).<br />
The device still registers button presses, as confirmed by the app animation when I press the button.<br />
But when I click into the action, it says "You need to set up a Spotify account to use this function." (already completed many times)<br />
So I click "Log In" -&gt; "Log In" and it logs me in automatically without entering any information (just a screen flicker - maybe it's grabbing the token from the browser).</p>
<p dir="auto">Is there any way to avoid this timeout on my credentials? It makes the integration completely unusable.</p>
<p dir="auto">Thanks for your help!</p>
<p dir="auto">Additional details:</p>
<ul>
<li>Samsung S22</li>
<li>Android 14 with One UI 6.1</li>
<li>Flic button connected via Hub Mini (bought last week)</li>
<li>Hub firmware is up to date (4.3.6)</li>
<li>I noticed the app said Android in power saving mode can cause issues, so I've confirmed this is not enabled</li>
</ul>
]]></description><link>https://community.flic.io/topic/18506/flic-with-spotify-loses-authentication</link><generator>RSS for Node</generator><lastBuildDate>Sat, 08 Aug 2026 09:49:04 GMT</lastBuildDate><atom:link href="https://community.flic.io/topic/18506.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 12 Dec 2024 23:33:32 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Flic with Spotify Loses Authentication on Mon, 10 Feb 2025 12:33:19 GMT]]></title><description><![CDATA[<p dir="auto">Hi, we have found the issue causing this in the Hub Firmware and a fix will be included in the next firmware release.</p>
]]></description><link>https://community.flic.io/post/21721</link><guid isPermaLink="true">https://community.flic.io/post/21721</guid><dc:creator><![CDATA[Emil]]></dc:creator><pubDate>Mon, 10 Feb 2025 12:33:19 GMT</pubDate></item></channel></rss>