-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Dev: Web - Console log error on clicking 'Confirm task' button #22824
Comments
Triggered auto assignment to @sophiepintoraetz ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to @yuwenmemon ( |
@yuwenmemon - asking for a friend here to reproduce, as I don't have access to a DEV environment! |
Dupe of #22853 |
It seems like this report came first though |
Actually, @Natnael-Guchima - looks like you are not correct - thanks @Santhosh-Sellavel! |
You are right. I didn't see the slack report since there were no slack link attached too the GH issue. Sorry for raising a wrong flag |
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:
Expected Result:
There should be no console error
Actual Result:
Console error is displayed [Provided collection doesn't have all its data belonging to the same parent.]
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: Dev 1.3.39-8
Reproducible in staging?: n/a
Reproducible in production?: n/a
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
Notes/Photos/Videos: Any additional supporting documentation
Screencast.from.2023-07-12.17-24-07.mp4
Expensify/Expensify Issue URL:
Issue reported by: @Natnael-Guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689172121893929
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: