I've been conducting a systematic evaluation of text-to-speech (TTS) tools for a productivity workflow analysis, and Speechify is a primary contender in my test cohort. However, I'm encountering a persistent technical issue that is severely compromising my ability to assess its reliability and, by extension, its value in a sustained workflow.
The core problem: the Speechify browser extension (v4.16.2) on Firefox (v128.0.2, Windows 11) repeatedly and unpredictably logs me out, requiring full re-authentication. This occurs across multiple profiles with varying extension sets. The logout appears to be triggered by:
* Firefox restart (nearly 100% reproducibility).
* Periods of inactivity exceeding ~30 minutes.
* Seemingly at random during active browsing sessions.
This is more than a minor inconvenience; it breaks key analytical workflows. For instance, I cannot maintain consistent session data for a longitudinal study of listening habits, and it invalidates any attempt at A/B testing listening speeds or voices across set content blocks.
My diagnostic steps thus far have included:
* **Clearing site data and cookies for Speechify domains:** Temporary fix, lasts {
console.log('Token persistence check:', result.authToken ? 'Present' : 'Null');
});
```
Has anyone else performing rigorous, long-term use of the Firefox extension encountered this? More importantly, are there any documented workarounds or confirmed fixes from Speechify's development team? Without a stable session, quantifying "time saved" or conducting any meaningful cohort analysis on my own usage is impossible, which significantly devalues the product's value proposition for data-driven users.
p-value < 0.05 or bust
Ugh, that sounds maddening, especially for a systematic evaluation. I ran into a similar login volatility issue with another extension last month during a cohort analysis, and it completely skewed my session duration data.
Have you checked if Firefox's "Enhanced Tracking Protection" or any of its cookie/partitioning settings are being overly aggressive with the extension's background page? I've seen that silently nuke session persistence before, because it treats the extension's authentication storage like a third-party tracker and purges it. The random mid-session logouts you mentioned scream something like that.
Your point about it breaking longitudinal study data is spot on, it turns a quantitative analysis into a guess. Have you tried forcing the extension's site permissions to "Allow" for all Speechify domains in about:preferences? That sometimes calms things down.
Try everything, keep what works.
That systematic approach is exactly right, and I've hit similar roadblocks with extension sessions breaking longitudinal data. Your mention of session data for listening habits is key, because it turns a controlled test into a reliability assessment.
I'd add one thing to your diagnostic list, based on a similar issue with an analytics tool: check if the extension is using a service worker for background tasks. Firefox's aggressive resource management can terminate them, and if the auth token is held there without proper persistent storage, it gets lost. The inactivity trigger you noted fits that pattern perfectly.
Have you tried creating a fresh Firefox profile, installing *only* Speechify, and seeing if the logout persists? That would isolate it from any other extension or setting interference.
ship early, test often
That systematic evaluation you're trying to do is exactly what gets torpedoed by this kind of flaky auth. I've seen it before with other SaaS extensions, and it usually points to a cheap implementation choice.
Your mention of it invalidating A/B testing is the real kicker. If they can't get a simple login session to persist, it makes you wonder what other corners they've cut with the actual TTS engine or data handling. I'd be less focused on Firefox settings at this point and more on what this says about their platform's stability for any long-term workflow. Have you checked if their mobile apps exhibit the same login volatility, or is this purely a web extension problem?
— skeptical but fair