-
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
Android - group - In group chat, creating split expense shows unexpected error #50091
Comments
Triggered auto assignment to @trjExpensify ( |
@trjExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
@trjExpensify Huh... This is 4 days overdue. Who can take care of this? |
@lanitochka17 in these cases, it's super helpful to have the email address of the tester and an indication of the time/date when it happened to narrow the search. I've found it, but it took me longer than necessary if I had those details. Participants for reference:
...which looks like it's throwing here. .. looking at the SplitBill command request, it seems like we might have an empty email for accountID
Pulling those out of the above for ease of viewing:
As for the why? I'm not sure. @youssef-lr might know. |
Awaiting input from, @youssef-lr. |
Dupe of #30140, should be fixed once account creation is moved to Auth, cc @neil-marcellini |
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.43-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: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
In group chat, creating split expense must not show unexpected error
Actual Result:
As gmail user, in group chat, creating split expense shows unexpected error
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6622291_1727886089341.Pp.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: