-
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
[Pay on 26-4][$1000] Native platforms crashing due to nbsp outside Text component #17414
Comments
Triggered auto assignment to @bfitzexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
@parasharrajat whipped up a PR soon and we merged it so that the app continues to work properly for our contributors. @bfitzexpensify, can you handle the payment for @situchan since they found the bug and @parasharrajat for the PR. |
@bfitzexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
PR merged |
Job added to Upwork: https://www.upwork.com/jobs/~011dca5d263f2f7434 |
Current assignee @bfitzexpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia ( |
Triggered auto assignment to @deetergp ( |
Added external to get the Upwork job created. Unassigning others. |
Not due yet. @parasharrajat can you link the PR so I can subscribe to it? |
Here you go #17412 |
Thanks! Updating the title of this issue so I know when to check back and issue payment |
Offers sent out @parasharrajat @situchan |
@bfitzexpensify 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! |
All paid out and contracts ended. We're all done here |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
https://expensify.slack.com/archives/C049HHMV9SM/p1681412584546029
Expected Result:
https://expensify.slack.com/archives/C049HHMV9SM/p1681412584546029
Actual Result:
https://expensify.slack.com/archives/C049HHMV9SM/p1681412584546029
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?
Version Number:
Reproducible in staging?:
Reproducible in production?:
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
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: