-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Messages sent on staging web are only appearing after navigate away from the report and run OpenReport again #51132
Comments
Triggered auto assignment to @justinpersaud ( |
Triggered auto assignment to @zanyrenney ( |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
Is this still happening? I am not able to reproduce |
Ok seems like I sort of was able to reproduce this. I left staging web open in the background for a few hours. I then went back to the tab and saw no new messages were posted in #social. However, I didn't do anything else and eventually it just updated everything at once. |
Yes it was happening to me this morning. I wasn't receiving updates until I navigated back to the report |
It's going to be tough to establish reproduction steps if you can't do it straight away, I thought it was an obvious regression but perhaps not |
Matt - do you mind taking this one if you're experiencing it? I can't access staging at all so it's not possible for me to test this? https://expensify.slack.com/archives/C049HHMV9SM/p1729158805892819 cc @muttmuure |
I think for this one, we need to trace the logs at the time, and understand if pusher was disconnected |
@muttmuure mind nailing down some of the specifics to help with the logsearch? I am seeing 93 instances of pusher in them. |
bump @muttmuure |
So to narrow this down, I think we should look for:
|
Cool, Matt - cheers! @justinpersaud do those Logs help you to push this forward? I don't think there is more the BZ can do here now Matt has got that log search. Thanks in advance! |
In the logs Matt provided I see this
Searching for that error, it seems this is not the first time we've seen similar issues I bumped the old thread https://expensify.slack.com/archives/C05LX9D6E07/p1730292728785699?thread_ts=1721217121.843389&cid=C05LX9D6E07 |
@chrispader I see you in the blame here for this https://github.com/Expensify/react-native-onyx/blob/main/lib/Onyx.ts#L274-L298 I think that is where the error above is coming from. Do you happen to have any ideas here? |
I'm going to be OOO next week but @chrispader said he would look into this later today. |
@justinpersaud @zanyrenney 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! |
hey @chrispader any update on this one, please? |
also bumped here - https://expensify.slack.com/archives/C05LX9D6E07/p1730743660837999 |
@justinpersaud, @zanyrenney Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Sorry for the delay. I'm looking into it later today! |
The highlighted code in
Therefore, i don't think this issue is directly caused by this code. We implemented this already a while back and so far, we didn't have any regressions because of this. (@justinpersaud, i know you're OOO so no hurry in answering, but how did you get to exactly this piece of code?) The main thing we had to migrate from since this change was that |
I couldn't reproduce this issue myself. I tried the repro steps but always received messages on both native device and (staging) web. Also i think the repro steps should be improved. E.g. in what state should each of the devices/sessions be? E.g. on the phone, should the app and chat be opened or not? Afaik, the user doesn't receive notifications when the app is in foreground. On web, should the affected report be focussed or not? |
@zanyrenney i can ofc continue investigating this issue if you want, but i'm not sure if someone else is supposed to fix this. I'd probably need some more repro steps in order to actually see this issue :) |
We’re waiting until @justinpersaud returns because he identified Chris in the blame, but Chris isn’t clear on why or how. If we want Chris to investigate, we can, but it would be helpful to get the missing context from Justin! |
Hey @justinpersaud - I think you're back from OOO now. Mind reviewing this and clarifying for us, please? Thanks! |
@chrispader I got there from the logs @muttmuure provided above. Here they are since you can't see them
I see that it was doing an onyx merge right before, so that is where I found that code. |
Hmm, so based on the logs i don't think this is an issue with the logic in I happen to have also worked on the
The merge executed on this key effectively just changes a number value. Therefore i don't think the following error ("Failed to write blobx") stems from this merge:
The last Since this issue is occurring on web, this is most likely caused by either (This might be related to storage being almost full.) |
As said before, i can start investigating this issue if you guys want, but i couldn't reproduce it the last time i tested, so any further repro steps and maybe more (detailed) logs would be very much appreciated! 🙌 |
I have been trying to reproduce but no luck here. |
We're going to close this off due to lack of reliable reproduction steps. Can revisit it again in the future if we see it https://expensify.slack.com/archives/C05LX9D6E07/p1731510575229519 |
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: @muttmuure
Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1729266448987419
Action Performed:
Expected Result:
Messages delivered to both the devices at the same time
Actual Result:
Not receiving messages in web on real time but getting push notifications for the same in app. Messages sent on staging web are only appearing after navigate away from the report and run OpenReport again
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
logs-2024-10-18 15_34_39.778.txt
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: