-
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
[$250 Internal] Notifications not being received #13392
Comments
Triggered auto assignment to @Christinadobrzyn ( |
I tested release builds as far back as Next guess is a backend change, which I'll look into next. |
Given that this already is on prod it should not be a deploy blocker, but it is a major issue that needs to be resolved ASAP |
I built a debuggable release build and discovered that we're hitting this condition. It makes sense that I'm not seeing notifications, but it does seem odd that this wasn't previously an issue. This is for local notification though which only affects web/desktop. I still need to figure out why Airship notifications have stopped. |
@robertjchen reports that he isn't receiving notifications on Android or Desktop. Perhaps this isn't just Android, I'll ask in Slack about iOS. |
Same to me. I haven't received any notifications recently even on web localhost. I remember this was working before. |
Thanks, but no this needs to be internal. It's critical, and is likely a backend issue. |
Focusing on the notification project in the meantime, which is more critical. |
We discussed this not being a deploy blocker and will fix after the notification doc has been released. |
Looking into these PRs:
I can confirm this is a recent config change issue, as I can receive notifications when directly targeting my device from the Airship console: |
Next step is to dive into the logs. I found examples of successful and failed notifications. Here's one of the failed messages. Notice that we route it via Pusher instead of Airship. Here are logs for a successful push notification send (from Chronos). Theories:
|
This comment was marked as off-topic.
This comment was marked as off-topic.
Just noting that my previous guesses were wrong 😅 I found the issue and a PR is in review |
Notifications are fixed -- just requires that users sign out and in again. Closing. |
@Julesssss Am I eligible for reporting bonus here? |
Yeah of course. My bad. @Christinadobrzyn could you please create an UpWork contract to pay a reporting bonus to @parasharrajat? Thanks |
Upwork job - Internal - https://www.upwork.com/ab/applicants/1603246366811955200/job-details Hired @parasharrajat as reporter for the $250 payment. @Julesssss or @parasharrajat can you confirm this job is finished and can be paid out/closed? I think it is based on the PR - https://github.com/Expensify/Web-Expensify/pull/35811 |
Hey @Christinadobrzyn, yep the PR was resolved and deployed. |
@parasharrajat when you have a moment, can you please accept the offer so I can pay you? Thanks! |
@Christinadobrzyn Accepted. |
Thanks @parasharrajat! I paid you as the reporter, closed the Upwork job and am closing this! Let me know if I've missed anything! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Problem
Multiple platforms are not receiving notifications in the production/staging environment.
Platform:
Where is this issue occurring?
Version Number: 1.2.33-7 1.2.34-1 1.2.35-0, 1.2.36-2,
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): ALL
Issue reported by: @parasharrajat
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1670408581155829
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: