-
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
[$500] You don't have access to this chat message appears when opening a report #51832
Comments
Triggered auto assignment to @muttmuure ( |
Triggered auto assignment to @MonilBhavsar ( |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
Followed up on https://expensify.slack.com/archives/C05LX9D6E07/p1730309258732469 |
@MonilBhavsar, @muttmuure 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
1 similar comment
@MonilBhavsar, @muttmuure 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
Looking into this |
@MonilBhavsar @muttmuure this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
|
@MonilBhavsar, @muttmuure Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@MonilBhavsar is this INTERNAL or EXTERNAL? |
Making it external Here is the theory #51832 (comment) Steps to reproduce :
|
@sobitneupane, @MonilBhavsar, @muttmuure Huh... This is 4 days overdue. Who can take care of this? |
Upwork job price has been updated to $500 |
Making $500 so we can get this fixed |
Hi, I am Michael (Mykhailo) from Callstack, an expert agency and I can work on this issue. |
Thanks Michael! This comment is a good summary of the issue #51832 (comment) I noticed the Onyx updates are not being applied sometimes and hence this issue. |
I've investigated the bug and tried to reproduce it a few times. Currently, I can see the problem with data sent by Pusher. There is a message from Pusher once user A deletes the workspace. This message contains updates to particular reports. However, it misses any values that point to closing/removing/archiving the #admin channel and expense report with other workspace members. It happens only when the user shifts between reports and invokes the OpenReport command. I see a solution where the backend sends more details (the Video
Bug.mp4 |
@sobitneupane @MonilBhavsar @muttmuure @rezkiy37 this issue is now 4 weeks old, please consider:
Thanks! |
Thanks for checking! |
I think I got the issue. Working and testing the fix |
I've got draft PR's up |
PR's are in review now |
@sobitneupane, @MonilBhavsar, @muttmuure, @rezkiy37 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@sobitneupane, @MonilBhavsar, @muttmuure, @rezkiy37 Huh... This is 4 days overdue. Who can take care of this? |
All PR's were deployed. @rezkiy37 thank you for your help in figuring this one out. Closing |
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:
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @davidcardoza
Slack conversation (hyperlinked to channel name): https://expensify.slack.com/archives/C05LX9D6E07/p1730309258732469
Action Performed:
Expected Result:
Able to access the account
Actual Result:
You don't have access to this chat message appears
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @MonilBhavsarThe text was updated successfully, but these errors were encountered: