-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 2022-03-22] [$500] Connection drop is not detected - Reported by: @Santhosh-Sellavel #6059
Comments
Triggered auto assignment to @Gonals ( |
Triggered auto assignment to @kadiealexander ( |
Nice catch! Added tags and sending to the pool |
Just going to reassign since I'll be OOO for the next wee while. |
Triggered auto assignment to @kevinksullivan ( |
@kevinksullivan Eep! 4 days overdue now. Issues have feelings too... |
Sorry couldn’t able to get here early @kevinksullivan
|
@kevinksullivan Whoops! This issue is 2 days overdue. Let's get this updated quick! |
When you say |
Cellular data @kevinksullivan |
Applied on Upwork, |
PR is ready: #7825 |
PR still in review. |
Very similar issue #7975 was fixed by the P.R. found in this issue. |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.42-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 2022-03-22. 🎊 |
@kidroca @Santhosh-Sellavel looks like the job expired so I created a new one and invited you. Once you submit I will hire and pay out the $500. Thanks! |
@kevinksullivan Should I apply on the same for C+? |
@pecanoro, @kidroca, @kevinksullivan, @parasharrajat Whoops! This issue is 2 days overdue. Let's get this updated quick! |
This is actually completed, I've applied to the new ticket and received payment |
Closing then! |
But Reporter and C+ are still not paid @kevinksullivan. |
I too received payment but for this, only C+ is missed out here for @parasharrajat. |
@kevinksullivan Bump. |
Apologies @parasharrajat . Just hired, please accept and I'll get this payment over. |
@kevinksullivan Done. |
@kidroca @kevinksullivan We reported the issue during Regression #8690 |
I've taken a look and it seems the Network code was (or is being) refactored If you want me to investigate further, please tag me on the new ticket |
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:
Connection drop should be detected on all circumstances.
Actual Result:
Connection drop is not detected and the app should online status.
Workaround:
None, going back online fixes the issue.
Platform:
Where is this issue occurring?
Version Number: 1.1.9-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @Santhosh-Sellavel
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1634766280030400
Job: https://www.upwork.com/jobs/~0129cfc8254ac008fa
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: