-
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 2024-01-11] [$500] Member - Gmail account cannot invite members to WS #32682
Comments
Triggered auto assignment to @puneetlath ( |
Job added to Upwork: https://www.upwork.com/jobs/~01c3f67ec9f72b91ef |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
Seems a backend issue where for Focus priority mode, workspace announce reports are not fetched in |
I cannot reproduce it on my end but based on the console error from the video looks like for whoever can reproduce it
I was able to reproduce it by setting |
@puneetlath Let's take this internal and assign an Engineer. Thanks. |
Let me know if you need C+ help here. For now, I unassigned as I think you won't. |
I was able to reproduce it by:
|
Adding to wave8. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Eep! 4 days overdue now. Issues have feelings too... |
1 similar comment
Eep! 4 days overdue now. Issues have feelings too... |
Copying my proposal from #33185. They have different console errors, but the same issue, and because it's marked as a dupe, I am posting my proposal here. ProposalPlease re-state the problem that we are trying to solve in this issue.The app throws an error if we change the priority mode to #focus, re-login, and trying to invite or remove a member from a workspace. What is the root cause of that problem?The error comes from this LOC where the app fails to find the announce report of the workspace. App/src/libs/actions/Policy.js Line 304 in c53eca9
It's because when we use a #focus mode, it will only load some required reports that will be shown on the LHN. When we update it back to Most recent, the app will trigger Lines 54 to 63 in c53eca9
What changes do you think we should make in order to solve the problem?If we can't find the announce report, that means nothing to update optimistically, so we can just return early. App/src/libs/actions/Policy.js Lines 297 to 303 in c53eca9
(we need to apply the same fix to |
Still overdue 6 days?! Let's take care of this! |
this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@bernhardoj's proposal sounds good. Let's go with it! |
📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
PR is ready cc: @parasharrajat |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.21-4 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-01-11. 🎊 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:
|
@parasharrajat friendly reminder about the checklist so that we can pay in a couple of days. |
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:
Regression Test Steps
Do you agree 👍 or 👎 ? |
This comment was marked as duplicate.
This comment was marked as duplicate.
Payment summary: Thanks everyone! |
Payment requested as per #32682 (comment) |
$500 approved for @parasharrajat |
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.9.1
Reproducible in staging?: y
Reproducible in production?: y
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:
Action Performed:
Prerequisites: Use [email protected]
account or other gmail account with existing WS
Expected Result:
The Gmail account should be able to invite members to any WS that exist in your account
Actual Result:
Gmail account cannot invite users to existing WS
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6304573_1701962022360.Recording__857.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: