-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 2024-12-03] [Search v1.2] - Button loads infinitely when approving or paying expense in Search in offline mode #52365
Comments
Triggered auto assignment to @madmax330 ( |
Triggered auto assignment to @stephanieelliott ( |
💬 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:
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Search - Button loads infinitely when approving or paying expense in Search in offline mode What is the root cause of that problem?When approving a money request on the search page, we update the isActionLoading flag to show the loading icon. However, since the request cannot be completed offline, the offline icon continues to display indefinitely. App/src/libs/actions/Search.ts Lines 202 to 204 in e3632a9
What changes do you think we should make in order to solve the problem?Solution 1: We can disable the approve button on the search page
Add new prop isDisabled, if isOffline is true and action is approve we will pass this prop is true and disable the button Solution 2: Show a modal when user click on the approve button to inform users that this action cannot be performed while offline
What alternative solutions did you explore? (Optional) |
I'm the author of the PR that introduced this functionality. I'll work on a fix |
PR in review |
Fixed in staging. |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.60-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 2024-11-20. 🎊 |
@luacmartins @stephanieelliott @luacmartins 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] |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.61-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 2024-11-21. 🎊 |
@luacmartins @luacmartins 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] |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.66-8 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 2024-12-03. 🎊 |
@luacmartins @luacmartins 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] |
This is done |
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.0.60-0
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Precondition:
Expected Result:
The expense is paid successfully in offline mode, or the button should be disabled if pay does not work in search in offline mode.
Actual Result:
The button loads infinitely when approving or paying expense in Search in offline mode.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6662139_1731391364441.20241112_140019.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @luacmartinsThe text was updated successfully, but these errors were encountered: