You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2025-02-04] [$250] Web - No login - first time go to Public room ulr, the link cut off leads to load infinitely #55239
Version Number: 9.0.85 Reproducible in staging?: Y Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Issue reported by: Applause - Internal Team
However, it's never available for anonymous users. So, the app will by default open with a report screen but without a reportID. We already have a logic to fill the reportID if it's missing by finding the last accessed report, but since we logged in as a new anon user, the public room is never accessed yet, so it returns nothing.
// We need skip deeplinking if the user hasn't completed the guided setup flow.
isOnboardingFlowCompleted({
onNotCompleted: startOnboardingFlow,
onCompleted: handleDeeplinkNavigation,
onCanceled: handleDeeplinkNavigation,
});
if (isAnonymousUser()) {
handleDeeplinkNavigation();
return;
}
// We need skip deeplinking if the user hasn't completed the guided setup flow.
isOnboardingFlowCompleted({
onNotCompleted: startOnboardingFlow,
onCompleted: handleDeeplinkNavigation,
onCanceled: handleDeeplinkNavigation,
});
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
N/A
What alternative solutions did you explore? (Optional)
If there is no last access/read report, fallback to the first report available.
changed the title [-]Web - No login - first time go to Public room ulr, the link cut off leads to load infinitely[/-][+][$250] Web - No login - first time go to Public room ulr, the link cut off leads to load infinitely[/+]on Jan 17, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.89-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@hungvu193@OfstadC@hungvu193 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Activity
melvin-bot commentedon Jan 14, 2025
Triggered auto assignment to @OfstadC (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.bernhardoj commentedon Jan 15, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
App loads infinitely when opening public room as anonymous user.
What is the root cause of that problem?
When we open a public room while logged out, it will trigger the OpenReport and we will be logged in as anonymous user.
App/src/libs/actions/Report.ts
Lines 2866 to 2873 in 7b9e55e
Then, the deep link to the public room will be handled after logged in and after the onboarding check.
App/src/libs/actions/Report.ts
Lines 2930 to 2934 in 7b9e55e
However, the above logic is never executed. The
isOnboardingFlowStatusKnownPromiseis never resolved.App/src/libs/actions/Welcome/index.ts
Lines 45 to 50 in 7b9e55e
It'll only be resolved if the nvp_onboarding data is available.
App/src/libs/actions/Welcome/index.ts
Lines 87 to 93 in 7b9e55e
However, it's never available for anonymous users. So, the app will by default open with a report screen but without a reportID. We already have a logic to fill the reportID if it's missing by finding the last accessed report, but since we logged in as a new anon user, the public room is never accessed yet, so it returns nothing.
App/src/pages/home/ReportScreen.tsx
Lines 153 to 162 in 7b9e55e
But it's not the problem here because the normal flow would be open public room -> logged in -> public room is shown, thus the report is read.
What changes do you think we should make in order to solve the problem?
We need to update the link handling. If it's an anonymous user, we don't need to check for onboarding data and just execute the link.
App/src/libs/actions/Report.ts
Lines 2929 to 2934 in 7b9e55e
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
N/A
What alternative solutions did you explore? (Optional)
If there is no last access/read report, fallback to the first report available.
App/src/libs/ReportUtils.ts
Line 1627 in 7b9e55e
OfstadC commentedon Jan 15, 2025
Will test this afternoon
OfstadC commentedon Jan 17, 2025
Was able to reproduce with this link
melvin-bot commentedon Jan 17, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021880330659956787723
[-]Web - No login - first time go to Public room ulr, the link cut off leads to load infinitely[/-][+][$250] Web - No login - first time go to Public room ulr, the link cut off leads to load infinitely[/+]melvin-bot commentedon Jan 17, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (
External)hungvu193 commentedon Jan 18, 2025
Will review today!
15 remaining items
melvin-bot commentedon Jan 28, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.89-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 2025-02-04. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 28, 2025
@hungvu193 @OfstadC @hungvu193 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
OfstadC commentedon Jan 28, 2025
@hungvu193 Please complete BZ Checklist prior to payment date! Thanks!
hungvu193 commentedon Feb 3, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: https://github.com/Expensify/App/pull/47097/files#r1938703740
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Feb 4, 2025
Payment Summary
Upwork Job
BugZero Checklist (@OfstadC)
OfstadC commentedon Feb 4, 2025
Payment Summary accurate
bernhardoj commentedon Feb 5, 2025
Requested in ND.
JmillsExpensify commentedon Feb 10, 2025
$250 approved for @bernhardoj
garrettmknight commentedon Feb 11, 2025
$250 approved for @hungvu193