-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2021-12-06] The Android hardware back button does not minimise the app when pressed on the LHN/home screen #4211
Comments
Triggered auto assignment to @mallenexpensify ( |
I don't have Android, trying to find someone on the CM team to triage |
Assigning to @laurenreidexpensify for review since she has Android and I don't. |
To me this is reproducible. |
@kp17211 @parasharrajat I'm trying to reproduce this and a bit confused.
Am I missing something? Isn't this the expected behaviour? |
This is an issue. the flow should be
|
Ah got it - okay yes I can confirm this is the behaviour then. Will send this to our engineering team for next review. |
Triggered auto assignment to @flodnv ( |
I could've sworn this was a feature and not a bug (granted, that I found strange as well). What's the behavior on iOS? |
I don't believe iOS has a "back" hardware button (at least most of their devices don't) so I think this only applies in Android. I agree this should be fixed eventually, it's how most (if not all) Android apps work, so I'll take this over and making it External Looks like these resources could be helpful:
|
Triggered auto assignment to @trjExpensify ( |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.12-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2021-11-09. 🎊 |
Hmm looks like this PR got reverted here: #6161 - @parasharrajat is looking into how to fix the issues that came from this PR |
not overdue, @parasharrajat is actively working on a fix in ^ PR |
Not overdue - fix is in staging, waiting to get to production |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.16-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2021-12-06. 🎊 |
Information for your reference.#5745 (comment) has the breakdown for payment. Please skip the milestone for 5027. Apart from it, there were two PR created for this issue. the first one #5745 went through N6-Hold and the second #6295 through Company Offsite Hold. |
Woof, this was a long one ey! So I presume from @mallenexpensify comment, this is the correct Upwork job, right? https://www.upwork.com/jobs/~017e60e720f6f9aca8 It's closed though and I couldn't see your proposal nor being hired Rajat, so we'll need to sort that out once confirmed this didn't move elsewhere. Then maybe @Beamanator can help confirm the total payable for this job at this point, skipping #5027. Am I reading it correctly that it should be $1,500? |
@Beamanator Could you please help us out here? |
I just looked through and I also believe payment should be $1,500. Breakdown:
@parasharrajat you thought your PR would also fix #5971, but we ended up closing it b/c it couldn't be reproduced, so no reward there. |
@Beamanator I am not sure about this but do you think the two bonuses apply here n6-hold and |
Hmm here's my thinking:
So I don't think that PR is eligible for the |
Correct. I overlooked it. Thanks. |
No prob at all |
Awesome. Offer sent 👍 |
All sorted, closing. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Actual Result:
Workaround:
Platform:
Where is this issue occurring?
Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Upwork URL: https://www.upwork.com/jobs/~017e60e720f6f9aca8
View all open jobs on Upwork
The text was updated successfully, but these errors were encountered: