Having migrated numerous enterprise authentication systems and relying heavily on MFA for administrative access, I've found the Okta Mobile app's performance on Android to be consistently and unacceptably subpar. While the underlying Okta service itself is robust for SSO and lifecycle management, the mobile client experience seems to be an afterthought, introducing significant friction and risk into daily workflows.
My primary issues, observed across multiple Android device models (Samsung Galaxy S23, Google Pixel 7) and Android versions (13 & 14), are as follows:
* **Persistent Session Expiration:** The app routinely logs itself out, despite selecting "Remember Me" and having a stable device posture. This defeats the purpose of a push notification flow, as I am forced to manually open the app and re-authenticate with a password and often another factor before I can even *see* the push notification I received. This happens at least 2-3 times per week per enrolled device.
* **Notification Delay and Unreliability:** There is a frequent, multi-minute lag between a login attempt triggering a push and the notification actually appearing on the device. In many cases, by the time the notification arrives, the originating browser session has already timed out. Furthermore, the "number" badge on the app icon often remains even after approving or denying the request, requiring a cache clear.
* **Background Service Aggressiveness:** The app appears to be aggressively killed by Android's battery optimization, even when all possible exemptions are applied. This is a known challenge on Android, but other critical auth apps (e.g., Microsoft Authenticator) manage far more reliable background processes.
From an architectural perspective, this suggests problems with either the FCM (Firebase Cloud Messaging) implementation, the local data persistence layer (likely SQLite), or the session token management within the app itself. The behavior points to tokens being stored in a volatile scope or being invalidated incorrectly by routine app lifecycle events.
**Workaround Attempts & Environment:**
I have performed standard troubleshooting: uninstall/reinstall, clear cache/data, ensure latest version (7.13.0 as of this writing), disable all battery optimizations for the app, and confirm stable network connectivity. None of these provide a lasting solution. The issue is observed on both cellular and Wi-Fi networks.
I am curious if other data professionals or platform engineers have encountered this and, more importantly, if anyone has discovered a systematic workaround or configuration change that improves reliability. This is particularly critical for those of us who manage production databases or ETL pipelines, where timely MFA approval is often the gating factor for incident response.
Given Okta's position in the enterprise market, this client-side instability is surprising. Has anyone engaged with Okta Support on this and received a meaningful response or seen these issues tracked on a public roadmap?
— Michelle
Query first, ask questions later.