Sorry for the delay, I was getting my Android phone working as well to test it there too.

My first few of these, so taking the template from StackOverflowTeams: https://stackoverflowteams.com/c/expensify/questions/14418

• The "bug" is actually a bug.
• The bug is not a duplicate report of an existing GH
• The bug is reproducible, following the reproduction steps.
• The GH template is filled out as fully as possible
• The GH was created by an Expensify employee or a QA tester.
• The bug is an /App issue

So, as we can see from my checklist, I don't see this still occurring.

iOS v12-58.4

Eugh, and my Android device still isn't working. Okay, in the meantime - I think this has self-resolved somehow. Could you confirm @kbecciv?

Okay, I tested this again today and I think this is a non-issue/resolved. Closing it.

@twisterdotcom Issue is still reproduced with build 1.2.64.3
Please type the message with lengthier letters like (j) and emoji, so you will be able to reproduce it.

Current assignee @twisterdotcom is eligible for the Bug assigner, not assigning anyone new.

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Okay, you're right? Yes, if it's a lower case letter than typically falls below the bottom line, it interferes ever so slightly with the next line, especially emoji. So q, j, g, y, and p I think:

Job added to Upwork: https://www.upwork.com/jobs/~01ebb233eae82dffea

Current assignee @twisterdotcom is eligible for the External assigner, not assigning anyone new.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External)

The BZ member will need to manually hire fabOnReact for the Contributor role. Please store your Upwork details and apply to our Upwork job so this process is automatic in the future!

Bump on this @fabOnReact

The BZ member will need to manually hire fabOnReact for the Contributor role. Please store your Upwork details and apply to our Upwork job so this process is automatic in the future!

I tried to apply for the Upwork job but it says that the job is no longer available.
I used this link https://www.upwork.com/jobs/~01ebb233eae82dffea
This is my Upwork profile https://www.upwork.com/freelancers/~01ae44247887fa908b?viewMode=1

Thanks

Offer sent: https://www.upwork.com/nx/wm/offer/102318386.

You can accept, but I think we still want to ensure that #4114 or #17767 won't actually resolve it anyway, and that your solution will work after that.

Update 17th May 2024

@twisterdotcom I wanted to let you know that I accepted the offer.

You can accept, but I think we still want to ensure that #4114 or #17767 won't actually resolve it anyway, and that your solution will work after that.

I tested a solution for this issue. I will publish the Pull Request with the solution in a couple of days. Thanks.

Update 21st May 2024

I published 2 PRs Expensify/react-native-live-markdown#350 and facebook/react-native#44614 to fix this issue. I will follow up in a couple of days. Thanks

Update 22 May 2024

• Merged PR Fix TextInput vertical alignment issue when using lineHeight prop on iOS without changing Text baseline (Fabric - new arch) react-native-live-markdown#350
• Meta imported PR Avoid setting a lineHeight lower of the fontSize lineHeight with Text and TextInput facebook/react-native#44614
• Published Draft PR upgrade react-native-live-markdown to 0.1.76 #42454 to update Expensify dependency react-native-live-markdown to 0.1.76. I will move it to Ready for Review tomorrow.

Update 23 May 2024

Moved PR #42454 to ready for review.

Update 28 May 2024

• PR #42454 merged
• I'll be away for 3 days for personal reasons (29, 30, 31st). I will restart working on Saturday 1st of June.

Reviewing label has been removed, please complete the "BugZero Checklist".

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.77-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• upgrade react-native-live-markdown to 0.1.76 #42454

If no regressions arise, payment will be issued on 2024-06-06. 🎊

For reference, here are some details about the assignees on this issue:

• @eVoloshchak requires payment through NewDot Manual Requests
• @fabOnReact requires payment (Needs manual offer from BZ)

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:

• [@eVoloshchak] The PR that introduced the bug has been identified. Link to the PR:
• [@eVoloshchak] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@eVoloshchak] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@eVoloshchak] Determine if we should create a regression test for this bug.
• [@eVoloshchak] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@twisterdotcom] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Update 1st of June 2024

PR #42454 was reverted because there are issues with react-native-live-markdown. The issues seem to not be related to PR Expensify/react-native-live-markdown#350.

• Chat - For quote, live markdown is not shown #42755 (Android)
• [$250] Android-Room-After creating room, entering @ not showing contact suggestions #42766 (Android)

I will look into it.