Closed IuliiaHerets closed 12 hours ago
Triggered auto assignment to @muttmuure (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
Triggered auto assignment to @blimpich (DeployBlockerCash
), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.
๐ฌ A slack conversation has been started in #expensify-open-source
:wave: 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:
App crashes when connecting to bank account.
we have this error Cannot access 'hasInProgressVBBA' before initialization
We should move function hasInProgressVBBA
to above place where we define the state shouldShowContinueSetupButton
here
Edited by proposal-police: This proposal was edited at 2024-11-04 16:51:33 UTC.
Bank account - App crashes when connecting to bank account
Long time ago https://github.com/Expensify/App/commit/98b1256be20fd2e43b4afa1426e885b0628b185f moved the call to getShouldShowContinueSetupButtonInitialValue()
above the place where the function is defined.
It was moved back in https://github.com/Expensify/App/pull/51315 but it recently got reverted by https://github.com/Expensify/App/pull/51857.
The PR after which this crash started to occur is https://github.com/Expensify/App/pull/51718. It changed
!requestorStepRef.current
to
!requestorStepRef?.current
I think this caused the compiler to generate a different lowered code. The following code seems to prevent the crash
!requestorStepRef || !requestorStepRef.current
Move this functions a few lines up before the call to getShouldShowContinueSetupButtonInitialValue()
Also avoid calling it again on every render
- const [shouldShowContinueSetupButton, setShouldShowContinueSetupButton] = useState(getShouldShowContinueSetupButtonInitialValue());
+ const [shouldShowContinueSetupButton, setShouldShowContinueSetupButton] = useState(getShouldShowContinueSetupButtonInitialValue);
I also see this bug today. But I don't understand why this bug happens after reverting https://github.com/Expensify/App/pull/51315. TBH, https://github.com/Expensify/App/pull/51315 fix another bug and we already reverted by https://github.com/Expensify/App/pull/51857. Anyone help to investigate why this bug doesn't happen before merging https://github.com/Expensify/App/pull/51315
cc @nkdengineer @CyberAndrii
Bringing conversation to Slack: https://expensify.slack.com/archives/C01GTK53T8Q/p1730736248203919
Job added to Upwork: https://www.upwork.com/jobs/~021853501012094691283
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 (External
)
Move this functions a few lines up before the call to getShouldShowContinueSetupButtonInitialValue()
@CyberAndrii I see your solution is no different from the solution I proposed before.
๐ฃ @DylanDylann ๐ An offer has been automatically sent to your Upwork account for the Contributor role ๐ Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review ๐งโ๐ป Keep in mind: Code of Conduct | Contributing ๐
๐ฃ @DylanDylann ๐ An offer has been automatically sent to your Upwork account for the Reviewer role ๐ Thanks for contributing to the Expensify app!
๐ฃ @CyberAndrii ๐ An offer has been automatically sent to your Upwork account for the Contributor role ๐ Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review ๐งโ๐ป Keep in mind: Code of Conduct | Contributing ๐
@ahmedGaber93 please ignore the ping, assigning @DylanDylann here since they have context
please ignore the ping, assigningย @DylanDylannย here since they have context
Ok, no problem, I also faced this problem yesterday and can help. It is a pretty straightforward JS issue and not requires any context.
@ahmedGaber93 thank you! We'll stick with @DylanDylann as the C+ for now but will let you know if we need help ๐
@nkdengineer hello there is definitely similarity with the proposals. I preemptively assigned @CyberAndrii since they were active in the Slack chat I opened up about this. My priority is to fix this quickly so I weighed their responsiveness in Slack heavily when assigning ๐
@blimpich thanks for explaining, i understand
Update: PR is up, waiting for @DylanDylann to come back online to review. I'm about to log off for the day, will check back in in the evening to see if PR is ready to merge and CP to staging.
TODO:
Thanks all. @blimpich, the changes looked good, so I have merged them to unblock the deploy. CP requested here.
Not reproduced Build v9.0.57-7
https://github.com/user-attachments/assets/c5496e75-e581-40e0-a99f-522036825bb8
Checked off
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 9.0.57-10 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-11-13. :confetti_ball:
For reference, here are some details about the assignees on this issue:
@DylanDylann @muttmuure 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 :rocket: deployed to production :rocket: in version 9.0.58-2 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-11-14. :confetti_ball:
For reference, here are some details about the assignees on this issue:
@DylanDylann @muttmuure 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]
@blimpich, @CyberAndrii, @muttmuure, @DylanDylann Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
[ ] [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:
[x] [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: https://expensify.slack.com/archives/C01GTK53T8Q/p1730736248203919
[x] [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[ ] [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Do we agree ๐ or ๐
@blimpich, @CyberAndrii, @muttmuure, @DylanDylann Eep! 4 days overdue now. Issues have feelings too...
@CyberAndrii - $250 for C @DylanDylann - $250 for C+
@blimpich, @CyberAndrii, @muttmuure, @DylanDylann Huh... This is 4 days overdue. Who can take care of this?
This is paid up and regression test created
If you havenโt already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.57-0 Reproducible in staging?: Y Reproducible in production?: N Email or phone of affected tester (no customers): applausetester+kh22100010ad@applause.expensifail.com Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
App will not crash when connecting to bank account.
Actual Result:
App crashes when connecting to bank account.
Workaround:
Unknown
Platforms:
Screenshots/Videos
0411_2.txt
https://github.com/user-attachments/assets/8a9f0e30-a382-412f-acf0-7b1adacdc431
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @muttmuure