-
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-10-23][$500] Send money - Extra two digits are added before the decimal point when money is sent offline #29318
Comments
Triggered auto assignment to @lschurr ( |
Bug0 Triage Checklist (Main S/O)
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @amyevans ( |
I am available right now, and can raise PR quickly if needed ProposalPlease re-state the problem that we are trying to solve in this issue.Send money - Extra two digits are added before the decimal point when money is sent offline What is the root cause of that problem?This is happening in all currencies. I think multiplying to Line 1939 in aff4623
Converting amount into smallest unit is happening here, so that amount is already in smallest units
What changes do you think we should make in order to solve the problem?We should remove this multiplication What alternative solutions did you explore? (Optional) |
Taking a look at the issue and then I will review the proposal, thanks. |
Thanks @techievivek! ❤️ |
@alitoshmatov This seems to happen even when we are online and click on the preview. Can you please quickly push a PR to fix this? I will be online to review and test it. |
Job added to Upwork: https://www.upwork.com/jobs/~01227f1e2615915351 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws ( |
📣 @alitoshmatov 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@techievivek On it! |
This comment was marked as abuse.
This comment was marked as abuse.
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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-10-23. 🎊 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:
|
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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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-10-23. 🎊 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:
|
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:
|
@amyevans, @lschurr, @techievivek, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Went through the BZ checklist: #29318 (comment) So all that's left is payments! |
Payment summary:
|
All done! |
@lschurr C+ payment is pending. Can you please reopen the issue? |
@situchan - @alitoshmatov was already paid in Upwork. Could you clarify what's missing? |
@lschurr ah, @alitoshmatov was C, I was C+ for this issue |
Ah, it looks like the automation missed that! I'll update the payment summary. |
Are you paid in Upwork or newdot @situchan? |
upwork |
Updated: #29318 (comment) |
Could you apply here @situchan? https://www.upwork.com/jobs/~01227f1e2615915351 |
Applied |
Payment issued. All set. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.3.81-4
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Note that in the report page, it shows RM900.00 instead of RM9
Expected Result:
The sent money in report page shows the correct amount, which is RM9.00
Actual Result:
The sent money in report page shows the incorrect amount, which is RM900.00. It shows the correct amount after going online
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Bug6232978_1697027336866.20231011_193721.mp4
MacOS: Desktop
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: