Open IuliiaHerets opened 1 month ago
Triggered auto assignment to @mallenexpensify (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
We think that this bug might be related to #vip-vsb
@mallenexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
Gonna try to pawn this off on Sheena when she gets assigned another iOS bug :)
Oh snap.... we got an Android phone on the way to the bank! I'll be able to test soon.
@mallenexpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Need to get Android phone setup, will do next week, bumped to Daily
Unsure when in the office this week but planning to get phone setup
@mallenexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Still need to get phone setup 😿
@mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.18 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4836262 Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
Inserting decimal point, behavior must be consistent in mweb& Android.
Actual Result:
In Android, decimal point is inserted correctly in the same place but in mweb, decimal point is inserted after a number. Inserting decimal point, inconsistent behavior in mweb& Android.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Screenshots/Videos
https://github.com/user-attachments/assets/343a82d9-0c96-43f1-ac9a-fa8f2c0c5c83
View all open jobs on GitHub