Closed lanitochka17 closed 1 year ago
Triggered auto assignment to @sophiepintoraetz (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
Platforms
in OP are ✅)The problem needs to be solved from backend. This problem is with another currencies as well. Ex - LBP.
The property coming from backend, ie. lastMessageText
and lastMessageHTML
is calculated wrong
Job added to Upwork: https://www.upwork.com/jobs/~0110273979413679a9
Current assignee @sophiepintoraetz is eligible for the External assigner, not assigning anyone new.
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (External
)
Assigning @sobitneupane to confirm that this is a backend issue!
@sophiepintoraetz It looks like a backend issue to me as well. It works fine in offline mode but as soon as connected to internet it changes to the wrong value. I believe it is due to some response from the backend.
https://github.com/Expensify/App/assets/25876548/bea8c2b3-48bf-413c-95ac-7009f9188c3e
Triggered auto assignment to @aldo-expensify (Engineering
), see https://stackoverflow.com/c/expensify/questions/4319 for more details.
I didn't have time to investigate this today, I'll try early next week.
@aldo-expensify - hopefully this week?
This is possibly because of:
Some code was added here changing the formatting used for IOU in the backend, but we didn't do anything in the App code to be consistent. This also makes more spread the code handling decimals in the backend. In the past this lived only in PHP-Libs https://github.com/Expensify/PHP-Libs/blob/main/src/CurrencyInfo.php.
I have already an issue for this: https://github.com/Expensify/Expensify/issues/300539
I'll try to give it time later during the week so we can get it done. Meanwhile, I think we can remove the help wanted and make it a weekly?
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@sobitneupane @sophiepintoraetz @aldo-expensify this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Removing Help Wanted
for now as this is most likely a backend problem
Current assignee @sobitneupane is eligible for the Internal assigner, not assigning anyone new.
I don't think this is happening anymore
https://github.com/Expensify/App/assets/87341702/8c9cebb3-f73d-4337-9b38-dee1e76c27dd
and with a bigger number 12345678
:
This feels like a duplicate of https://github.com/Expensify/App/issues/19792 and it was solved when the solution for that ones deployed I think.
Oops, I think I was having problems with my dev env and this is not working really! reopening to keep investigating
Confirmed that this bug still exists:
The frontend seems to be sending an incorrect amount to the backend. The amount should be in "cents" (1/100 subunit) independent of the currency used.
Creating a money request of 100 USD (2 decimals currency), should send an mount of 10,000 to the backend Creating a money request of 100 LAK (0 decimals currency), should send an mount of 10,000 to the backend
In the screenshot above, the expected amount was 1234567800
, but it wasn't multiplied by 100
Frontend PR up: https://github.com/Expensify/App/pull/24175 Taking videos/screenshots
I wasn't able to finish, my PR is causing a regression described here: https://github.com/Expensify/App/pull/24175#issuecomment-1666333579
I'll continue on Tuesday 👋
Didn't continue on Tuesday, but I finished the code for https://github.com/Expensify/App/pull/24175 today. I just have to complete the testing steps and provide more screenshots, then I'll make it ready for review.
I made the PR ready for review today.
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 1.3.55-8 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-08-28. :confetti_ball:
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:
@sobitneupane - can you put in a request for $1000 once you have completed the checklist above?
Bump @sobitneupane
Sorry for the delay. I will try to get to it by tomorrow EOD.
Bump @sobitneupane
Closing in the meantime - seeing as the action is with @sobitneupane and the request summary is here.
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:
I think this issue was caused by some backend change as suggested here
Regression Test Proposal:
Create money requests in currencies that have decimals and currencies without decimals, for example:
Verify that preview looks correctly formatted in chat report and in LHN.
Do we agree 👍 or 👎
Requested payment on newDot.
https://github.com/Expensify/App/issues/23235#issuecomment-1695016076
$1,000 approved for payment in NewDot based on this BZ comment.
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:
The amount in LAK currency on the badge is displayed correctly and is equal to the amount owed by the participant
Actual Result:
The amount in LAK currency on the badge is displayed incorrectly, the last two digits of the amount owed are missing
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.43.0
Reproducible in staging?: Yes
Reproducible in production?: Yes
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
https://github.com/Expensify/App/assets/78819774/57eca6a8-6448-400b-bc12-b9fd547ccf85
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Upwork Automation - Do Not Edit