-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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 2025-02-04] [$250] Web - No login - first time go to Public room ulr, the link cut off leads to load infinitely #55239
Comments
Triggered auto assignment to @OfstadC ( |
ProposalPlease 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 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. Line 1627 in 7b9e55e
|
Will test this afternoon |
Was able to reproduce with this link ![]() |
Job added to Upwork: https://www.upwork.com/jobs/~021880330659956787723 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 ( |
Will review today! |
Thanks @bernhardoj. Your proposal looks good to me! 🎀 👀 🎀 |
Triggered auto assignment to @thienlnam, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
PR is ready cc: @hungvu193 |
|
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:
|
@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] |
@hungvu193 Please complete BZ Checklist prior to payment date! Thanks! |
BugZero Checklist:
Bug classificationSource of bug:
Where bug was reported:
Who reported the bug:
Regression Test ProposalPrecondition:Test:
Do we agree 👍 or 👎 |
Payment Summary
BugZero Checklist (@OfstadC)
|
Payment Summary accurate |
Requested in ND. |
$250 approved for @bernhardoj |
$250 approved for @hungvu193 |
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: 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
Action Performed:
Precondition: Create a public room and copy URL
Expected Result:
Public room should open
Actual Result:
Page loads infinitely, ulr is changed to "https://staging.new.expensify.com/r"
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6709624_1736397135276.Recording__837.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @OfstadCThe text was updated successfully, but these errors were encountered: