-
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 2023-12-29] [HOLD for payment 2023-12-28] Desktop - Sign In - Console error Uncaught (in promise) TypeError: Cannot read properties #33290
Comments
👋 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:
|
Triggered auto assignment to @marcochavezf ( |
I haven't seen this yet, I will be afk for a couple of hours and check it out when I return. |
Ok I found the cause of the problem, creating a PR to fix it |
PR up |
Triggered auto assignment to @joekaufmanexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Hi @joekaufmanexpensify, could you pay for the C+ review for @allroundexperts? |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.14-6 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 2023-12-28. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
|
Per this, payment may be delayed a few days here because of the holidays. @allroundexperts if you have time over the next week to handle the BZ checklist too, that'd be great! |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.15-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 2023-12-29. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Not overdue, checklist is still pending |
Issue is ready for payment but no BZ is assigned. @MitchExpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
|
Not sure why I was assigned, looks like @joekaufmanexpensify is on the case |
Yep! Just need @allroundexperts to handle BZ checklist and then I'll issue payment. |
@marcochavezf, @allroundexperts, @joekaufmanexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Still discussing in Slack |
Checklist
Do we 👍 or 👎 ? |
TY! Checklist is done. All set to issue payment. |
Only payment needed here is $500 to @allroundexperts for C+ review. Paid via NewDot. |
@allroundexperts could you please request $500 and comment here once you've done that? |
Chatted with @allroundexperts and confirmed good to close. |
$500 payment to @allroundexperts based on this comment. |
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: 1.4.14-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR #31303
Action Performed:
Expected Result:
Console errors should not be displayed
Actual Result:
Console error displayed
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6319675_1702994068266.Screen_Recording_2023-12-19_at_15.51.30.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: