-
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
Android - Reimburse expenses - the rate value is reset to zero after the system allows entering more than three digits after the dot, error message displayed after. #11058
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @Justicea83 ( |
This can be external |
Triggered auto assignment to @stephanieelliott ( |
@Justicea83 this is a deploy blocker and should be handled internally because of urgency in the fix. Removing the |
Ohk, thanks for picking it up, wraping up here |
I can reproduce inputting more than 3 digits on android and iOS, however I could not reproduce the error message nor the value being reset to 0. |
Interesting, have you managed to identify a clear pattern of when it happens? I'm trying the same exact steps as the video and randomly minimizing/reopening the app but can't reproduce (on Android). I wonder if it could have something to do with this PR: #10468. |
The error message suggests that the policy has been updated while we were offline, so maybe going offline and editing the policy on OldDot would trigger the error? I'm triggering that error on dev, but the rate is reset to the original amount after the call fails and the error is shown. |
@kbecciv we are having issues reproducing the rate being reset to 0. Is this consistently reproducible for you? |
I believe not, I didn't experience anything even close to this!
Is this the expected, as far as I know we will round off to three digits.
This is issue due to internet failure. Turn off internet try changing values after some time resume internet I see 0.000 and error even on iOS check out the video below. RPReplay_Final1663351187.MP4@francoisl @luacmartins hope this clarifies, thanks! |
@luacmartins Yes, two testers was able to reproduce it. Screen_Recording_20220916-084224_New.Expensify.mp4 |
I checked the recent android build, it always gets reset to |
I was able to reproduce reliably as well, but I also see the problem in prod. I'll remove the blocker label and make this an external issue. |
Actually, I'll keep this one internal since it might involve the new API command. |
I did some testing and it seems like that issue 1, is caused by the delay between the input and setState re-rendering the component on mobile. In the past, we got around this by using |
I see this in the logs:
|
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. |
I'm still focused on API refactors, but I have a hunch that we might be able to solve the 3 digits issue by using an uncontrolled input. |
I'll try to get to this next week! |
We have two distinct bugs here
I'm gonna keep this issue open and monitor it to make sure it's solved. |
Issue not reproducible during KI retests. (First week) |
I can't reproduce 1 anymore. Now we are down to offline edits being reset when we come back online which should be resolved by #12219 |
Ok cool, so then I'll update the hold and re-test when that one is merged. |
Still waiting on #12219 to merge. |
#12219 is merged. Gonna retest this. |
This issue was fixed by #12219! 🎉 android.movClosing. Please reopen if needed. |
Oh nice! Thanks for jumping on that so quickly and testing! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Issue found when executing PR #10974
Action Performed:
Expected Result:
Actual Result:
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.1.0
Reproducible in staging?: Yes
Reproducible in production?: No
Email or phone of affected tester (no customers): any
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Bug5734721_10468_Android_FAIL.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: