-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-03-24] Android - Help panel - Incorrect navigation with device back button when help panel is opened #57840
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
Comments
Triggered auto assignment to @lschurr ( |
Triggered auto assignment to @madmax330 ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
What's the deal with this one @madmax330? Should it be External? |
Maybe @puneetlath since you changed it to Daily.. is this still happening and should it be External? |
Responded in NewDot. |
Both issues are still reproduced. Screen_Recording_20250311_232606_Expensify.mp4 |
Hey! I’m Błażej Kustra from Software Mansion, this regression comes from my #56490 so I'd like to work on it 👀 |
It is very connected to the other issue for iOS. Help pane isn't technically a screen so you can't dismiss it with a back button and swipe gesture. I need to check what we can do with this, will update tomorrow. |
Update: I opened a draft PR for this 🚀 |
PR is ready for C+ review, could you assign @brunovjk to this issue? 😄 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.13-5 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 2025-03-24. 🎊 For reference, here are some details about the assignees on this issue:
|
@madmax330 @lschurr @blazejkustra The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
This issue is part of some regressions during the implementation of Help Panel. I think we can follow the payment on the original issues. |
Great, so we're good to close this one @brunovjk @blazejkustra @madmax330? |
I think so, but I'm not sure if we need to fill out the BZ checklist here. I'll confirm on Slack and get back to you. |
I can't reproduce this anymore after implementing this PR. Tested on 27 Mar v9.1.20-2 Develop. We can close, payment and BZ checklist will be handled here. Thanks! |
Uh oh!
There was an error while loading. Please reload this page.
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.1.9-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy Z Fold 4 / Android 14
App Component: Other
Action Performed:
Precondition:
Bug 1:
Bug 2:
Expected Result:
Bug 1:
Bug 2:
Actual Result:
Bug 1:
Bug 2:
Workaround:
Unknown
Platforms:
Screenshots/Videos
https://github.com/user-attachments/assets/d0722519-5de0-47ab-b2c8-742f1c150fdb
https://github.com/user-attachments/assets/3cfda779-5a4c-4d8b-902c-026b0297452d
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @lschurrIssue Owner
Current Issue Owner: @lschurrThe text was updated successfully, but these errors were encountered: