Mobile app back button navigation issue.

[OmMakwana221]

About

When navigating inside the app (e.g., going through 4–5 screens/tabs), if I press the default mobile back button, the app closes directly instead of going back to the previous screen.

Expected Behavior

The default back button should follow single-page-wise navigation (go back one screen at a time) instead of closing the entire app.

Question

Is this behavior configurable or fixable in the current version?

1. Can I implement per-page back navigation using the default mobile back button?
2. Or is this a known bug that your team plans to resolve in a future release?

[OmMakwana221]

Hi team,

I created this issue 2 days ago and I wanted to ask if there are any updates or guidance available. I am continuously working on it, but the back button behavior is still not working as expected. Even a small hint or direction from your side would be really helpful.

Thanks a lot for your support!

[hharkovenko]

Hi. Can you please share a little bit more info, mobile app version, affected platform(Android/IOS) (that's why we have "Bug" issue template).
In general it looks like a known issue that is planned to be resolved with 1.8 release.

[OmMakwana221]

Hi, thanks for your reply . Let me share more details so it’s clearer:

Mobile App Version: 1.7.0
Platform: Android

Steps to reproduce:

1. Open the app and log in.
2. Navigate deeper into the app, for example open 4–5 different screens/tabs one after another. like any dashboard states one by one.
3. Press the default Android back button (the system back button, not the in-app navigation).
4. Instead of going back screen by screen, the entire app closes immediately.

Expected behavior:
The back button should behave like normal navigation — going back one page at a time until reaching the main/home screen.

Actual behavior:
The app exits directly after pressing the back button, no matter how deep I am in the navigation stack.

I hope this gives a clearer picture of the issue.

[OmMakwana221]

Hi @hharkovenko ,
I just wanted to ask if there is any solution or workaround available right now — maybe through a code file change — since this fix is urgently required on my side.

Really appreciate any guidance you can share. Thanks!

[hharkovenko]

Hi.There is no easy code fix for this. To fix this I need to rewrite whole routing logic of the app, I'm working on it right now. If you really need this fix as soon as possible I'll tag you here so you can grab code from dev branch when it will be ready