Repository navigation
[Due for payment 2025-04-08] Endless loading screen when launching New Expensify Desktop app after update #59184
Description
Activity
- addedAutoAssignerNewDotQualityUsed to assign quality issues to engineersUsed to assign quality issues to engineersBugSomething is broken. Auto assigns a BugZero manager.Something is broken. Auto assigns a BugZero manager.DailyKSv2KSv2Needs ReproductionReproducible steps neededReproducible steps neededretest-weeklyApply this label if you want this issue tested on a Weekly basis by ApplauseApply this label if you want this issue tested on a Weekly basis by Applause
on Mar 26, 2025 Triggered auto assignment to @blimpich (
AutoAssignerNewDotQuality)Triggered auto assignment to @miljakljajic (
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.This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
This is the error Ryan ran into
Uncaught (in promise) TypeError: Failed to execute 'add' on 'Cache': Request scheme 'app' is unsupported6 remaining items
- addedAwaiting PaymentAuto-added when associated PR is deployed to productionAuto-added when associated PR is deployed to production
on Apr 1, 2025 - changed the title
[-]Endless loading screen when launching New Expensify Desktop app after update[/-][+][Due for payment 2025-04-08] Endless loading screen when launching New Expensify Desktop app after update[/+]on Apr 1, 2025 Reviewinglabel has been removed, please complete the "BugZero Checklist".The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.21-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 2025-04-08. 🎊
@mountiny @miljakljajic @mountiny 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]
$250 to @jayeshmangwani
I dont think we will need a regression test for this one as its edge case
Reacted by Jayesh MangwaniPayment Summary
- Reviewer: @jayeshmangwani owed $250 via NewDot
BugZero Checklist (@miljakljajic)
- I have verified the correct assignees and roles are listed above and updated the necessary manual offers
- I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
- I have paid out the Upwork contracts or cancelled the ones that are incorrect
- I have verified the payment summary above is correct
Closing as Vit has shared a payment summary above, and no additional tests needed.
$250 approved for @jayeshmangwani
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
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:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @ryanldonato
Slack conversation (hyperlinked to channel name): #Quality
Action Performed:
Expected Result:
The application should load successfully, allowing access to expenses and reports.
Actual Result:
The application does not load beyond the initial screen and displays a continuous loading circle.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
The Video for the issue is in OP
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @miljakljajic