-
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
[HOLD for payment 2023-11-30] Notification - User is navigated to LHN after opening notification when app is closed #31625
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
📣 @github-actions[bot]! 📣
|
Triggered auto assignment to @johnmlee101 ( |
Production : Screen_Recording_20231121_144726_One.UI.Home.mp4 |
I managed to reproduce on staging even when online screen-20231121-110843.mp4 |
We drop the onyx data from the notification payload once it reaches 3.5kb. I wonder if recent additions to the onyx payloads have once again broken push notifications (cc@arosiclair) |
cc @arosiclair |
BTW https://www.expensify.com/_devportal/tools/logSearch/#sort=asc&size=5000&query=blob%3A%22Logging%20request%20details%22%20AND%20email%3A%22john%40expensify.com%22%20AND%20timestamp%3A%5B2023-11-21T00%3A00%20TO%202023-11-22T23%3A59%5D this seems to be 3k characters in the request, but not sure if thats going down the right path |
Keeping some discussion here: https://expensify.slack.com/archives/C07J32337/p1700588638959299?thread_ts=1700588255.529729&cid=C07J32337 But this was logged in some of the requests
|
I can reproduce this in dev. It seems like there are no issues with handling the notification click:
however it looks like there's code navigating back to the home page after we navigate to the chat which is breaking this functionality:
Maybe one of this deploy's PRs added an extra navigation that's doing this?
|
Removing the blocker label since we CPed a fix. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.2-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-11-30. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
|
@johnmlee101 Huh... This is 4 days overdue. Who can take care of this? |
1 similar comment
@johnmlee101 Huh... This is 4 days overdue. Who can take care of this? |
I think @arosiclair fixed this with the linked PR and we can close it, right? I assigned him to give him credit since he created the PR to fix it. |
This should be all set so closing this out |
@arosiclair can you please reopen and add |
Triggered auto assignment to @laurenreidexpensify ( |
This comment was marked as off-topic.
This comment was marked as off-topic.
@laurenreidexpensify can you handle payment for @aimane-chnaif's C+ review? Thanks! |
Payment Summary: C+ Review - $500 @aimane-chnaif Offer sent in Upwork https://www.upwork.com/en-gb/jobs/~01a9cda98c1c4a1734 |
Payment Summary: C+ Review - $500 @aimane-chnaif paid in Upwork |
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: 1.4.1.7
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
User is navigated to the correct chat
Actual Result:
User is navigated to the LHN
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6285512_1700573648641.video_2023-11-20_22-01-24.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @laurenreidexpensifyThe text was updated successfully, but these errors were encountered: