App: [HOLD for payment 2023-06-23] [$1000] Invalid html code with large digit crashes android app and throws console error on other platforms
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:
- Open the app in android
- Open any report
- Send invalid html code with large digit eg:
�
Expected Result:
App shouldn’t crash or provide console error on sending invalid html codes with large digit
Actual Result:
App crashes in android and provides console error on other devices when we send invalid html codes with large digit
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
- Android / native
- Android / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
Version Number: 1.3.20-0 Reproducible in staging?: y Reproducible in production?: y 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/43996225/62235857-75dd-4e44-acd6-8365e8d14418
https://github.com/Expensify/App/assets/43996225/76f983d8-2c4f-45b1-bc5b-33ae7dbcbf89
Expensify/Expensify Issue URL: Issue reported by: @dhanashree-sawant Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1685098437111809
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~0137581aed483fd0c3
- Upwork Job ID: 1663778192565182464
- Last Price Increase: 2023-06-07
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 49 (23 by maintainers)
hired @hungvu193 @eVoloshchak and @dhanashree-sawant
@hungvu193’s proposal looks good to me! Both proposals are essentially the same, while @hungvu193 was the first to propose a fix.
I think ideally we just update the html-entities version
🎀👀🎀 C+ reviewed! cc: @iwiznia
Agree! Let’s fix this issue upstream
Yeah, that’s wrong, because I created the PR in expensify-common, and it was merged within 2 days. Also the PR I created in this repo was also merged within 2 days. https://github.com/Expensify/expensify-common/pull/545 (Created on 9 Jun and was merged on 10 Jun)
payment issued!
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one 🚀