Android Back Navigation Closes the App Instead of Returning to the Previous Screen

Applies to: Mattermost Mobile App v2.41.0 and later (Android)

Symptoms: On Android, using the hardware/three-button back button or the edge-swipe-back gesture closes the app instead of returning to the previous screen, in most attempts.

🛑 Problem

Starting with mobile app v2.41.0, Android back navigation (the hardware/three-button back button, or the right-edge-swipe gesture) can fail to return the user to the previous in-app screen and instead exits the app entirely, as if the app had no navigation history. This affects most back-navigation attempts, not an isolated screen, and is independent of server version.

Symptoms

There is no server-side error or log entry for this issue; it is a client-side navigation defect. Administrators and users will see:

• Pressing back (hardware button or edge-swipe) on Android closes the Mattermost app instead of navigating to the previous screen.
• The on-screen header back arrow, where present, continues to work correctly and is not affected.
• The issue is intermittent per navigation attempt, but occurs in most attempts once present.

Additional symptoms:

• Reproduces regardless of Mattermost Server version (confirmed independently against multiple server versions).
• Not tied to license tier or any specific System Console setting.
• Can persist across sessions until the app's local storage is cleared, then can recur later.

✅ Solution

There is no server-side or configuration fix; this is a defect in the mobile app's Android navigation handling introduced by the v2.41.0 release. Apply the following in order.

Clear the App's Local Storage

Resetting the app's local storage clears cached navigation state and has resolved the symptom for affected users:

• Open Settings on the Android device.
• Go to Apps (or Apps & notifications).
• Select Mattermost from the list.
• Tap Force stop, then confirm.
• Tap Storage & cache (or Storage).
• Tap Clear storage (or Clear data), then confirm.

⚠️ Important: Clearing storage signs the user out. They will need to log back in with their server URL and credentials afterward.

Use the On-Screen Back Arrow if the Issue Recurs

The underlying navigation defect is not yet fixed as of the current app release, so the symptom can return after clearing storage. If it does, use the on-screen header back arrow instead of the hardware back button or edge-swipe gesture; the header back arrow does not go through the affected navigation path and is not impacted.

Additional Resources

No public documentation page exists yet for this issue; it is tracked internally with the mobile engineering team as a known, unresolved Android navigation defect.