Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Back button pressed from settings moves app to the previously opened activity #1102

Open
apoorva-mk opened this issue Mar 10, 2019 · 2 comments

Comments

@apoorva-mk
Copy link

apoorva-mk commented Mar 10, 2019

Summary:

If the back button is pressed from the settings activity it moves to the previously opened navigation menu tab and not the home page unlike other options

Steps to reproduce:

  • Open Setting from the Home screen Navigation drawer.
  • Select Beneficiaries
  • Open Navigation menu and click on Settings
  • Press Back Button
  • It shows the Beneficiaries activity again.
  • Same issue not seen with other options in the menu

Expected behavior:

Expected to open the Home Activity

Observed behavior:

Instead reverts to previously opened activity

Device and Android version:

Redmi Y2

@apoorva-mk apoorva-mk reopened this Mar 10, 2019
@apoorva-mk apoorva-mk changed the title no internet Back button pressed from settings moves app to the previously opened activity Mar 10, 2019
@apoorva-mk
Copy link
Author

I believe issue #1009 and #891 are along similar lines but the bug I raised is still present and is inconsistent with the expected outcome. I'd like to work on this.

@gururani-abhishek
Copy link
Contributor

gururani-abhishek commented May 13, 2023

@jawidMuhammadi , isn't this how the default functioning should be, if I go to beneficiaries -> then I go to settings -> if I press a back, I should be taken back to what I was doing before(i.e. was in beneficiaries screen).
And recently we also worked on this issue, where we purposefully wanted the user to land back to the previous screen if we tap back from the settings. Have a look : #2076
If you agree then we can also close this issue and related PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants