Two different problems get reported the same way. In the first, Sprecho drops you back to the login screen — after a restart, after the lid was closed, or seemingly at random. In the second, Sprecho still shows you as signed in while things quietly stop working: dictionary entries will not save, history stops updating, and restarting the app fixes it for a while.
Both come from the same place — the sign-in token that Sprecho renews in the background. And both have been genuine bugs in the app at some point, not something you did wrong.
Try this first
- Open Settings → System → Updates and install any available version. This is the fix for the large majority of reports.
- Go to Settings → Account → Security and sign out, then sign in again. This replaces whatever stale credentials are on the device.
- Check that your device's date, time and time zone are set automatically.
- If you are on a company network, ask IT to allow
api.sprecho.ai— see below for what specifically needs to pass.
Older versions really did have this bug
We would rather say this plainly than have you chase your own setup.
Until version 2.50.4, an expired sign-in token could not always be renewed while the app was running. The result was exactly the second symptom above: the app looked signed in, but dictionary saves, transcript sync, statistics and notifications all failed silently, and only a restart brought them back. It is fixed in 2.50.5, and the last remaining cases — including one that affected device management and one on mobile that surfaced roughly 30 days after signing in — are fixed in 2.50.6.
Two older ones are also worth knowing about, in case you are on an old build:
- Signed out on every sleep or restart. If the network was not back yet when the app tried to renew, the app treated it as a rejection and cleared the session. Fixed in 2.39.1; a temporary network failure now never signs you out.
- Asked for a verification code that never arrives. A failed startup check could leave a verified account looking unverified, and the app would send you to a code screen for a code that is not coming. Fixed in 2.47.1.
If restarting Sprecho reliably repairs things for an hour or so, you are on a build with the first bug. Update.
Signed in, but nothing syncs
The tell-tale sign is that a restart helps and then the problem returns. Update first. If you are already current and still see it, note whether everything stopped at once or only one feature did — that is what narrows it down.
How long a session is supposed to last
Sprecho holds two credentials. The short one is renewed automatically about once an hour while the app is running. The long one keeps you signed in for 30 days without a successful renewal, which is why an offline laptop or a week's holiday does not sign you out.
You have to sign in again when the app genuinely could not reach Sprecho for longer than 30 days, when you signed out, or when an administrator removed your access.
Check your clock and time zone
Sign-in tokens carry an expiry timestamp, compared against your device's clock with no tolerance. A clock off by an hour or more — a dual-boot machine, a suspended virtual machine, a manually set time zone — makes valid credentials look expired, or expired ones look valid.
Turn on automatic date and time (System Settings → General → Date & Time on macOS, Settings → Time & language → Date & time on Windows), then sign out and in again.
Company networks, proxies and firewalls
Sprecho needs two kinds of connection to api.sprecho.ai: ordinary HTTPS, and a
WebSocket connection for live sync. Many corporate setups allow the first and
silently drop the second — which produces the confusing state where sign-in
works, the app looks healthy, and background sync never happens.
Ask your IT team to allow both https://api.sprecho.ai and
wss://api.sprecho.ai, plus sprecho.ai for downloads and updates. If your
network inspects TLS traffic, that inspection is worth naming in your support
ticket, because it changes what the app can do.
Symptom → cause
| What you see | What it usually is |
|---|---|
| Signed in, but syncing stops until you restart | The token-refresh bug in builds before 2.50.5 — update |
| Login screen after every sleep or restart | An old build clearing the session on a temporary network failure — fixed in 2.39.1 |
| Asked for a verification code that never arrives | An old build misreading your verified status — fixed in 2.47.1 |
| Signed out on one device only | That device's clock is wrong, or it was offline for more than 30 days |
| Sign-in works, nothing else does | A proxy or firewall is blocking the WebSocket connection |
| Signed out on mobile about a month after signing in | The mobile token bug fixed in 2.50.6 — update the app |
Still stuck?
Contact support and include your Sprecho version from Settings → System → Updates, whether restarting the app helps temporarily, and whether you are on a company network. Collect logs for support explains what else to attach so the first reply can be a real answer.