Sign-in required

"Sign-in required" came back

This means the platform refused to renew the stored access, and only signing in again fixes it. Connections → Channels → Reconnect. Nothing else helps: there is no repair button and no way to refresh it from the outside.

It often shows up an hour or two into a session rather than at startup, because access is renewed on a timer while the app runs, not when it starts.

Nothing needs saving afterwards, Kick included: once the browser sign-in lands, the module picks up the new access by itself within a few seconds.

Nothing happened after the browser window

The settings pages of Twitch, YouTube, Kick and DonationAlerts say what they are waiting for. Right after the button: "Finish signing in in the browser window — this page will update on its own." After two minutes: "Still waiting for the browser…". That is not a failure: finish the sign-in in the browser and the page updates itself. On Twitch, pressing the button again in the meantime cancels the sign-in that is open in the browser, so finish that one first.

If the confirmation was declined or the browser window was closed, the page cannot tell straight away and keeps waiting until its limit: 10 minutes for Kick, 15 for YouTube and DonationAlerts, 30 for Twitch. Then it says "Sign-in did not finish. The browser window was closed or the request was declined — press the button to try again." Start the sign-in again.

Twitch says CONNECTING… and stays there

Twitch counts as connected only when both halves are alive — the chat connection and the event subscription. Stuck on CONNECTING… means the second half did not come up. Reconnect; if it repeats, that is worth a support request with the log attached.

Twitch: a feature quietly does nothing

Most often the account has no permission for that feature — see the guide "Signing in to platforms", section "Twitch: granted permissions".

Kick: "channel not found" or no chat

Two common causes, and both are handled on the Kick page: see the guide "Signing in to platforms", section "Kick: channel address and Chatroom ID".

A third cause has nothing to do with your channel. On October 13, 2026 Kick changed how apps connect to its chat, and from that day Kick chat stopped reaching strAImer versions before 0.25.0: commands, the chat overlay and the bot's replies went quiet on Kick, and the Kick row on Connections → Channels shows ERROR. Signing in again does not help, and neither does checking the channel address or the Chatroom ID, because nothing was wrong with them. Updating does: strAImer 0.25.0 asks Kick for the current connection details each time it connects to the chat, and the chat comes in again. Your version is shown under the logo; the update is in Settings → Updates, as the guide "Updates" describes.

YouTube says CONNECTED but there is no chat

Between streams this is expected: CONNECTED then means you are signed in and the app is waiting for your next broadcast.

During a stream, from strAImer 0.25.0, the badge turns green only once YouTube has answered the app's chat request. So green with an empty chat while you are live most often means the app has not found the broadcast yet. A stream visible only by link can take up to half an hour to be found, as the guide "YouTube Integration" explains, and a permission unticked on the Google sign-in screen keeps it from ever being found: see the article "Connected, but nothing arrives". On earlier versions the badge could stay green while the chat had failed to start.

YouTube shows CONNECTING... or ERROR during a stream

The broadcast was found, but its chat has not started. CONNECTING... is the wait for YouTube's first answer. ERROR means starting the chat failed; the app tries again once a minute on its own, and there is nothing to press. The badge stays red until the chat answers or the stream ends, and then goes back to CONNECTED. What each badge means is in the guide "Signing in to platforms", section "YouTube: chat arrives with the broadcast".

If it stays red for the whole stream, the Log console has a line starting with "Failed to connect to Live Chat" followed by the reason. That is worth a support request with the log attached; the guide "Help" says how.

YouTube says "Sign in again", yet the chat still comes in

Expected: the stored sign-in expired, and the app keeps reading your public stream and its chat without it. What waits for a new sign-in is sending messages as you, streams visible only by link, and moderation other than through the bot. Sign in again on the YouTube page; the guide "YouTube Integration" describes what the page shows.