0.11.24

The framework you picked is the one that runs — and one that cannot sign in now says so instead of quietly filling your computer with processes.

Fixes

• Your framework starts, and answers — Tesseract could hand a framework the sign-in details meant for a different one. It then had nothing it could use, fell back to a service it was not signed in to, and every message died before a reply — while the app still showed the framework as connected. It now gets its own details, and works.
• The sign-in tab looks like Tesseract, and tells you the truth — The page your browser lands on after signing in with Google showed the wrong logo, and counted down to closing itself — which browsers do not allow for a tab they opened. It now carries the real mark and simply tells you the key that closes it.
• A framework that cannot start no longer piles up in the background — When a framework failed to start, Tesseract kept launching fresh copies and left the old ones running — dozens within a couple of minutes, quietly using memory until you restarted. Each attempt now cleans up after itself.

---

Updating from inside the app: Settings → About → Check for updates. See the full list in the app under What's New.