-
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 2024-04-15] [HOLD for payment 2024-04-09] Thread - App shows skeleton loading when clicking on parent/ancestor message offline #39264
Comments
Triggered auto assignment to @arosiclair ( |
👋 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:
|
We think that this bug might be related to #vip-vsb |
I reproduced. It seems like navigation back to the parent does not work while offline. @rayane-djouah @allroundexperts @chiragsalian can any of you guys take a look? |
Seems like it's due to |
We used comment linking feature in the "Thread" and header links to navigate directly to the message as requested here: #38722 (comment). Seems like comment linking requires connectivity. I think that in offline mode we should navigate to the report when clicking the links like we used to do before. Do you agree @allroundexperts ? |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
Partial revert merged : #39302 |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
Gonna remove the blocker because the revert PR above appears to have fixed this and was CP'd. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.58-8 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 2024-04-09. 🎊 |
Handled in another issue. |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.60-13 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 2024-04-15. 🎊 |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.58-0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #38722
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
App will redirect to the relevant thread without skeleton loading.
Actual Result:
App shows infinite skeleton loading when clicking on parent/ancestor message offline.
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6431721_1711726259481.20240329_232816.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: