-
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 2023-08-08] [HOLD for payment 2023-08-07] Web - 'You'll lose any offline changes if you sign-out.' message appears even if you are online #23742
Comments
Triggered auto assignment to @slafortune ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.When clicking on the Sign Out button, the user is shown the confirmation dialog when the user is online. What is the root cause of that problem?This is a regression caused by #22153. The logic is incorrect for this line: App/src/pages/settings/InitialSettingsPage.js Line 147 in cd09dc9
What changes do you think we should make in order to solve the problem?We should negate the What alternative solutions did you explore? (Optional)None |
This is regression from #16281 (comment) |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @mountiny ( |
@mountiny @slafortune this is a regression from #16281. Awaiting response from contributor on this. |
@mananjadhav given its deploy blocker and the contributor hasnt messaged I have created the PR |
@mountiny I’ll be able go check this in an hour, afk |
No problem merged going to CP |
@slafortune Can we pay @gadhiyamanan $250 for reporting this bug? |
@gadhiyamanan offer sent here - https://www.upwork.com/nx/wm/offer/25815360 |
@slafortune offer accepted, thanks! |
Thanks - Paid! |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.47-6 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-08-07. 🎊 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.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.48-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-08-08. 🎊 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.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
user should be Sign out
Actual Result:
shows 'You'll lose any offline changes if you sign-out.' message even if you are online
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.47.2
Reproducible in staging?: Yes
Reproducible in production?: No
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
Screen.Recording.2023-07-27.at.11.15.08.AM.mov
Recording.3956.mp4
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690436737183979
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: