Web - New group - Console error when creating new group

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Go to URL https://staging.new.expensify.com/
2. Log with any account
3. Click on FAB button/New Group
4. Select multiple users
5. Click "Create group"

Expected Result:

There should not be any errors in the console

Actual Result:

An error appears in the console

Workaround:

unknown

Platform:

Where is this issue occurring?

• Web

Version Number: v1.2.20-1
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Bug5795228_Recording__2590.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @youssef-lr (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[melvin-bot]

Triggered auto assignment to @adelekennedy (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

@youssef-lr, @adelekennedy Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@youssef-lr, @adelekennedy Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[youssef-lr]

I can reproduce this. This is most likely an issue coming from the server, I will investigate this more when I'm done with an API refactor.

[michaelhaxhiu]

This is most likely an issue coming from the server

Does that mean internal in this case? Let's get the appropriate label assigned so Adele can help drive it forward per this process to keep the pressure on to find a contributor and get this one closed out

[michaelhaxhiu]

PS all bugs should be daily

[youssef-lr]

@michaelhaxhiu I just added the internal label. Unassigning myself as I'm busy with an API refactor.

[adelekennedy]

internal now - @youssef-lr what are next steps to add an engineer to this issue the SO is unclear what the follow up is afterwards.

[melvin-bot]

Triggered auto assignment to @Gonals (Demolition), see https://stackoverflow.com/c/expensify/questions/8099 for more details.

[arielgreen]

Adding demolition per this thread.

[melvin-bot]

@Gonals Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@Gonals Still overdue 6 days?! Let's take care of this!

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[michaelhaxhiu]

That's good it's not reproducible this week. But this doesn't have a BZ assigned and it should 🤔 .

[melvin-bot]

Triggered auto assignment to @alexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[alexpensify]

@michaelhaxhiu - I'm confused with this one. Do I need to create a job in Upwork? I see it's internal, so I don't think creating a job is the right step. Any feedback will help!

[alexpensify]

Ok, confirmed this is an Internal one. @Gonals flagging that this one looks similar to this GH:

#12637

One difference is the other GH is for inviting members instead of creating a group. If yes, I think we should close one and merge them together. Thoughts?

[Gonals]

Ok, confirmed this is an Internal one. @Gonals flagging that this one looks similar to this GH:

#12637

One difference is the other GH is for inviting members instead of creating a group. If yes, I think we should close one and merge them together. Thoughts?

They seem different to me. The displayed error is not the same, so the underlying cause (and the fix) is likely different.

I'll take a look and see if we can still reproduce this. If we can, I'll fix it. Otherwise, I'll just go ahead and close it

[Gonals]

Unable to reproduce in either Staging, Prod or Dev. Closing