-
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 2023-06-01] [$1000] Loading screen appears every time on app open even if user is not logged in #18172
Comments
Triggered auto assignment to @laurenreidexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Reproduced on Android. Adding to Upwork |
Job added to Upwork: https://www.upwork.com/jobs/~0184a1af5983832ede |
Current assignee @laurenreidexpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
Totally thuoght I put label on yesterday 🤦♀️ |
Triggered auto assignment to @tylerkaraszewski ( |
I think it is expected behavior since regardless of logged in state, and caused by: App/src/libs/Navigation/NavigationRoot.js Lines 55 to 59 in e0772ac
|
Looks like something related to As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our Feel free to drop a note in #expensify-open-source with any questions. |
This will be fixed in #17477 |
@0xmiroslav so are you advising to close? |
@laurenreidexpensify Let’s hold it until the PR is merged |
Looks like we think this is going to be fixed by a PR from @zoontek, so I'm assigning this to him to remove the |
This is indeed fixed in #17477. It was caused by the |
📣 @zoontek You have been assigned to this job by @roryabraham! |
@laurenreidexpensify accepted, thanks! |
@laurenreidexpensify I am not eligible for compensation here as it was fixed by other PR. |
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. |
Not blocker anymore, Melvin! It was fixed earlier. |
@tylerkaraszewski, @zoontek, @fedirjh, @laurenreidexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
PR has been merged , hasn’t hit staging yet. |
On Staging now #17477 (comment) |
I am also eligible for C+ compensation for reviewing PR |
@laurenreidexpensify can you please assign the issue to @0xmiroslav as he reviewed the related PR. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.17-5 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 2023-06-01. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
📣 @0xmiroslav You have been assigned to this job by @laurenreidexpensify! |
@zoontek @gadhiyamanan have been paid in Upwork. Sorry @0xmiroslav missed the message to add you to the issue - have sent proposal in Upwork, can you complete the checklist above? Thanks |
No PR caused regression. Regression Test Proposal
|
Perfect - Regression test requested https://github.com/Expensify/Expensify/issues/288069 |
Also - payment has been issued in Upwork now! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
should not show loading screen if user is not logged in
Actual Result:
loading screen appears every time even if user is not logged in
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.8-4
Reproducible in staging?: y
Reproducible in production?: y
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
Notes/Photos/Videos: Any additional supporting documentation
az_recorder_20230428_170411.1.mp4
Screen_Recording_20230428_230519_New.Expensify.mp4
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1682703466457829
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: