-
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
Messages not appearing on desktop. New message appeared as iOS notification even though desktop app is open. #9958
Comments
Triggered auto assignment to @sakluger ( |
@yuwenmemon think this could be related to the change here: App/src/libs/actions/Session/index.js Line 464 in da22ec6
? I'm wondering why we did not end up in this block if the issue was an expired App/src/libs/actions/Session/index.js Lines 471 to 475 in da22ec6
We also didn't make it here: App/src/libs/actions/Session/index.js Lines 479 to 483 in da22ec6
Which means we threw in
Looked a bit deeper and I think that will only happen if we are processing the request in the App/src/libs/Middleware/Reauthentication.js Lines 36 to 46 in c45e58f
we don't pass a promise that can be resolved when calling First solution that comes to mind is to allow Line 87 in c45e58f
If we do this then Pusher would be able to handle it's reauthentication. |
Actually, we probably don't want to do that because it would persist those requests and we don't really need to do that. 🤔 |
Figured it out and more context in PR. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
When we start the New Expensify desktop app we should be subscribed to Pusher and notifications about new messages should appear on desktop.
Actual Result:
Pusher failed to subscribe to the private user channel (necessary to receive chat messages) and new messages were sent as device push notifications (iOS) instead despite being online and having the Desktop app open.
Workaround:
Refreshing the app
command + r
or closing and reopening seems to resolve this and fix the broken Pusher connection.Platform:
Version Number: 1.1.84.12
Reproducible in staging?: Yes
Reproducible in production?: Unknown
Email or phone of affected tester (no customers):
Logs:
Notes/Photos/Videos:
I'm unsure how to reproduce this reliably, but it seems related to the authToken expiring and something about the reauthentication and sequential queue is maybe not working quite right. I tried to create a repro by invalidating the token manually and closing then reopening the app, but Pusher connected fine in this case.
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: