[$500] Desktop - Reload - ''Hmm... it's not here'' when reloading the desktop app

[lanitochka17]

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.1-5
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:

1. Launch the desktop app
2. Press Cmd + R or click on the View menu, then select ''Reload''

Expected Result:

No errors should be encountered when reloading the app

Actual Result:

When reloading the app, a 'page not found' error is displayed
Hmm... it's not here
Oops, this page cannot be found
Go back to home page

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

@

Bug6284623_1700518933812.Error_when_press_cmd__R.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01fc65658e91d3dd1c
• Upwork Job ID: 1726776353641140224
• Last Price Increase: 2023-11-21

[melvin-bot]

Triggered auto assignment to @deetergp (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[lanitochka17]

Production:

Screen.Recording.2023-11-20.at.19.21.05.mov

[luacmartins]

I can reproduce this and see the following logs. It seems like we're intentionally navigating to that page.

[info] Navigating to route - {"path":"/not-found"}

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01fc65658e91d3dd1c

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt (External)

[erquhart]

Likely same root cause as #28495, may be a dupe.

[tienifr]

I posted a proposal on the other issue, it will fix this one as well

[situchan]

Not able to reproduce on main. Or does this happen only in release build?

[situchan]

@tienifr this is deploy blocker so there must be offending PR recently merged. #28495 was open for a while.

[tienifr]

Not able to reproduce on main. Or does this happen only in release build?

@situchan yes it's only on release build

[situchan]

For me, this happens on android chrome as well. Still interesting that not reproducible on iOS safari.

not.found.mov

[tienifr]

For me, this happens on android chrome as well.

@situchan Yeah it’s because your https://127.0.0.1 is not in the whitelisted prefixes as well, we can optionally add that to the prefix list for development convenience.

[situchan]

I just reproduced this today. I have been testing with https://127.0.0.1/ so far after https integration but used to work fine.

[situchan]

So I can conclude that @tienifr's solution is just workaround without fixing the root cause.
We should really find out the offending PR.

[s77rt]

This may be a dupe. I think this issue existed for a while but due to another factor the bug is constantly reproducible now.

I tested this on v1.3.83-0. The bug is there but not very easy to reproduce

Screen.Recording.2023-11-21.at.6.13.29.PM.mov

[mallenexpensify]

Been working on a similar issue for weeks that might be related. I'm also getting the 'hmm' error after every time I've updated the app the past two days.
#28495

[mallenexpensify]

From Tim G in this internal thread, in case it's helpful:

1. If there is a reportID in the URL, load that report. (if you do not have access to that report, you are shown "not found")
2. Sort all reports in Onyx by their lastReadTime
3. if openOnAdminRoom param is in the URL, then fine the first report where the chat type is policyAdmins and assign it to the variable adminReport
4. If isFirstTimeNewExpensifyUser and there is only 1 sorted report, load that report
5. If there is more than 1 sorted report, and there is adminReport, load the first sorted report that is not concierge
6. If they are not in the domain rooms beta
7. filter the sorted reports to only contain non-domain chats, workspace chats, chats with their guides
8. If adminReport exists, load it
9. else load the last sorted report

The bulk of that logic is here: https://github.com/Expensify/App/blob/main/src/libs/ReportUtils.js#L596-L631

[s77rt]

@tienifr Any idea why is the initial url app://- Can we change it?

[luacmartins]

This seems to be a dupe of #28495 and given the video @s77rt shared, it seems like a race condition that was made worse with the last deploy. I'm gonna remove the deploy blocker label since this is already happening in previous versions, just not as noticeable. We need to keep investigating and fix this though.

[s77rt]

@luacmartins Shouldn't we close this one?

[luacmartins]

Yea, we should be good to close.