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

Pressing back button from any footer functionalities exits the app without prompting user. #1228

Open
3 tasks done
msaini888 opened this issue May 10, 2020 · 8 comments · May be fixed by #1879
Open
3 tasks done

Pressing back button from any footer functionalities exits the app without prompting user. #1228

msaini888 opened this issue May 10, 2020 · 8 comments · May be fixed by #1879
Assignees
Labels
bug Something isn't working client Mobile client/app component P2 "Nice to have" - shipping next version without this will not have a major impact source:qa From QA team

Comments

@msaini888
Copy link

msaini888 commented May 10, 2020

Description

When a user finishes the onboarding permissions and lands on the application home screen, then pressing the back button from Stats, Learn, Check-up, Settings directly kills the app without giving a prompt to the user.

Solution

If the user is on any other functionality other then Home functionality in the footer then pressing the back button from mobile should take the user back to the Home screen tab and further press of back button should give a pop up to the user asking "Are you sure you want to exit the app?" with okay and cancel button.

This is observed on the 0.8.0 version of the app on various Android OS like Android 8.0, 9.0, 6.0.

  • Searched the existing issues to ensure you are not creating a duplicate.
  • Followed the Contributor Guidelines.
  • Issue has a descriptive title focused on the feature or problem from the user's perspective
@msaini888 msaini888 added needs:triage New issue that needs triage source:public Issues created by the public idea Ideas for app features source:qa From QA team and removed source:public Issues created by the public labels May 10, 2020
@Khaoz-Topsy
Copy link

I volunteer 👋

@msaini888
Copy link
Author

@Khaoz-Topsy : thanks for taking this up but please check with @hspinks or @advayDev1 before you start working on this.

@advayDev1 advayDev1 added this to the v1.0 - Nigeria milestone Aug 17, 2020
@advayDev1 advayDev1 added bug Something isn't working client Mobile client/app component and removed needs:triage New issue that needs triage idea Ideas for app features labels Aug 17, 2020
@brunobowden
Copy link
Collaborator

@Khaoz-Topsy - please check if this still happens. If so, then we'd welcome a PR to fix it.

@brunobowden
Copy link
Collaborator

@Mohit020888 - please confirm this still happens

@msaini888
Copy link
Author

@brunobowden - yes this issue is still reproducible on app version 0.14.0 (25)

@brunobowden brunobowden added the P2 "Nice to have" - shipping next version without this will not have a major impact label Nov 9, 2020
@brunobowden
Copy link
Collaborator

@Mohit020888 - I've marked it P2. Do you consider it more important than that?

@msaini888
Copy link
Author

@brunobowden - Yes P2 is the correct priority for this one Bruno !

@brunobowden
Copy link
Collaborator

@Mohit020888 - thanks. Please feel free to add P0, P1 or P2 labels to bugs, or even adjust existing ones if they look obviously wrong. Just add a note briefly explaining why.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working client Mobile client/app component P2 "Nice to have" - shipping next version without this will not have a major impact source:qa From QA team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants