Google sign-in keeps looping
Check that the provider is enabled for the deployment, the redirect domain is authorized, and the browser has not blocked the pop-up or callback.
Common fixes
Fix the usual blockers fast.
When a LiteVerse screen does not behave as expected, start with the account, the provider, and the live connection. Most issues come from sign-in state, browser storage, or provider configuration.
Most problems fall into one of these buckets.
Session restore does not finish
Wait for the loading state to finish, then check whether the account already has a newer active session on another device.
Logs stop updating
Confirm that the live endpoint is still connected and that the app is not hiding the stream behind a collapsed panel.
Android sign-in feels wrong
Use the native Android login flow when Google is enabled. If a browser loop appears, try email/password and report the device and app version.
When something looks stale, check the basics first.
Before you retry login
Refresh once and watch for the loading state.
Confirm the account selection matches the one you want.
Check whether another device already has the same session open.
Make sure the redirect domain belongs to LiteVerse.
If the screen is still wrong
Sign out of the account on the current device.
Close the app or browser tab and open it again.
Clear the browser site data when the web flow is stuck.
Use the dashboard to confirm which nodes are actually linked.