v2.13.0
Bug fixes
Self-hosted (Docker): task creation broken on local network access
Users accessing the Docker container via a LAN IP address over HTTP (e.g. http://192.168.1.x:7191) could not create tasks — the "Add to Schedule" button and all other task creation actions appeared to do nothing. This affected Chrome, Firefox, and Safari equally. Root cause: crypto.randomUUID() is only available in secure contexts (HTTPS or localhost); accessing over HTTP on a non-localhost address silently removed the API, causing a TypeError on every task creation attempt. Fixed with a standards-compliant fallback using crypto.getRandomValues(), which has no context restriction.
Self-hosted (Docker): service worker updates not delivered after initial install
A nginx location priority bug caused the service worker (sw.js) to be served with a one-year immutable cache instead of the intended no-cache headers, meaning Docker users would never receive app updates once the service worker was cached. Fixed by switching the affected locations to exact-match rules, which take priority over the regex asset-caching block.
Cloud sync: spurious "Encryption key not available" error on startup
When cloud sync with encryption was enabled, a brief race between app load and passphrase/key initialisation could cause a failed upload attempt before the session key was ready. This produced a misleading console error — no data was ever lost and the engine recovered automatically — but the noise made it look like a hard failure. The debounced upload now waits for the key to be ready before firing.
Internal
Added an access code bypass to the subscription wall for app store reviewer compliance (Play Console App access policy / Apple App Review Guideline 2.1).