I've been conducting a thorough evaluation of the Consensus platform over the past quarter, primarily focused on its API reliability and session management as it relates to my automated cost-query workflows. However, a persistent and frankly disruptive issue has emerged during my mobile testing phase: the iOS application exhibits a chronic inability to maintain an authenticated session.
The behavior is consistent and reproducible across multiple devices (iPhone 13 and iPad Pro, both on latest OS). The app will function normally for a period ranging from a few hours to, at most, a day. Upon returning to the app—whether from the background or a cold start—I am invariably presented with the login screen. This occurs despite having "Keep me logged in" selected and despite no system-level memory pressures or battery optimizations that should affect session cookies or tokens.
This has several tangible impacts on my usage patterns:
* It interrupts the ability to quickly reference a previous search or cost query while on the go, which is a key value proposition of a mobile companion app.
* It necessitates repeated entry of credentials, which is a security concern when using a password manager on a mobile device in public spaces.
* It breaks the expected state synchronization between the web console and the mobile app, as I am constantly having to re-establish my authenticated context.
From a technical perspective, this suggests one of several potential root causes in the mobile implementation:
* An overly aggressive or misconfigured token TTL (Time-To-Live) on the mobile client, not respecting the refresh token cycle.
* A failure to securely persist the session keychain items between app launches.
* A server-side session management policy that treats mobile app sessions differently from web sessions, perhaps invalidating them after a shorter inactivity period.
Has anyone else in the community encountered this specific mobile app behavior? I am particularly interested if Android users are seeing the same pattern, or if this is isolated to the iOS build. Furthermore, has anyone discovered any workarounds—such as specific notification settings, background app refresh configurations, or account security settings—that mitigate this frequent logout issue?
I intend to include this reliability metric in my ongoing cost-benefit analysis of the platform, as support overhead and workflow friction have direct, if sometimes hidden, operational costs.
-- Liam
Always check the data transfer costs.