Repository navigation
Erebrus AI 1.1.1
Version: 1.1.1+3
| Artifact | Platform |
|---|---|
erebrus-ai-dappstore-v1.1.1.apk |
Solana Mobile / dApp Store (dApp Store key) |
erebrus-ai-linux-v1.1.1.tar.gz |
Linux bundle (x64) |
erebrus-ai-playstore-v1.1.1.aab |
Android App Bundle for the Play Console (Play Store key) |
erebrus-ai-playstore-v1.1.1.apk |
Android sideload (Play Store key) |
erebrus-ai-r8-mapping-v1.1.1.zip |
R8 mapping files for deobfuscating Android stack traces |
erebrus-ai-windows-v1.1.1.zip |
Windows |
erebrus-ai-manifest-v1.1.1.json |
Release manifest (sizes, SHA-256, signing certificates) |
erebrus-ai-sha256sums-v1.1.1.txt |
Checksums (sha256sum -c erebrus-ai-sha256sums-v1.1.1.txt) |
Both APKs use com.erebrus.ai with different certificates — install one.
Changes
Sign-in
- Stay signed in: the app adopts the gateway's rotating refresh sessions and
renews the access token in the background before it expires, instead of
signing you out after 24 hours. Existing logins upgrade once, silently. - Network errors, timeouts, rate limits and gateway errors no longer sign you
out or clear account, organization or entitlement data. When a session
cannot be renewed safely, Settings shows Sign in again and keeps your
local data. - A suspended account is signed out with a suspension message instead of
"session expired". - Sign-out revokes the session on the gateway, and says so when revocation
could not be confirmed (for example while offline). - Signing out or switching accounts mid-request can no longer show the
previous account's data. - Session credentials live in an app-specific Keychain/Keystore namespace,
excluded from Android backups and device transfer. - Android: launch no longer hangs when Android recreates the app in a process
the background-serving service kept alive. - Gateway requests identify the platform (Android, iOS or desktop), so the
account activity log shows where you signed in.
Builds and releases
- Push a
v*tag matchingpubspec.yamlto publish a GitHub Release: signed
Play Store APK + App Bundle and dApp Store APK (certificates verified), Windows
and Linux packages, a release manifest and SHA-256 checksums, with notes taken
from this changelog. macOS joins once CI signing is configured. - CI scans the git history for secrets and builds every platform again: Apple
builds use Xcode 26+ (needed for on-device transcription), the generated
Swift package is pinned to iOS 17 / macOS 14, Linux installs the GStreamer
and app-indicator libraries, the Android NDK install no longer fails, and the
Windows TurboQuant runtime install is completed whenflutter buildstops
early. - Apple CI builds install Xcode's separately shipped Metal toolchain, which
the on-device MLX runtime needs to compile its GPU shaders. - The Android TurboQuant cross-compile no longer stops on a fresh checkout.
- The Linux and Windows runtime checks no longer depend on
llama-server --versionoutput, which reports this repository's commit instead of
TurboQuant's; the pinned source is still verified by checksum. - Failed build steps repeat their errors as workflow annotations, readable
without signing in to GitHub. - Android release builds are shrunk and obfuscated with R8 again (it was
turned off when the store flavors were added, which Play Console flagged as
1% obfuscation). The App Bundle carries its mapping file, and each GitHub
Release attaches the mapping files for the APKs.