[HOLD for payment 2025-02-06] [HOLD for payment 2025-02-05] [$250] Chat - Bold markdown gets triplicated when used as a second markdown in an emoji.

[IuliiaHerets]

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.84-0
Reproducible in staging?: Yes
Reproducible in production?: No
Email or phone of affected tester (no customers): ibellicotest+171@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome
App Component: Other

Action Performed:

1. Open the staging.new.expensify.com website.
2. Open any chat.
3. Compose a message with two markdowns, being the second one "Bold" and an emoji. Example: :smile
4. Check the bold markdown behaviour with this action.

Expected Result:

Bold markdown should be displayed only once when used as a second markdown on an emoji.

Actual Result:

Bold markdown gets triplicated when used as second markdown in an emoji message.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6711634_1736579064916.Bold.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021881676503226665257
• Upwork Job ID: 1881676503226665257
• Last Price Increase: 2025-01-21

Issue Owner

Current Issue Owner: @abekkala

[melvin-bot]

Triggered auto assignment to @abekkala (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.

[melvin-bot]

Triggered auto assignment to @grgia (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[shubham1206agra]

@mountiny Please reopen this issue.

[Skalakid]

Is this issue still reproducible? Markdown syntaxes seem to work fine on the latest staging and dev

Screen.Recording.2025-01-13.at.10.37.20.mov

[Skalakid]

Oh I see, it occurs on the latest version of the Live Markdown

[Skalakid]

Hello, since the problem is serious and might be blocking another deploy, we decided to fix it by disabling splitting ranges on emojis on the web. Afterward, we will focus on enhancing the web parser to make it more bug-proof and flexible for range lengths. The more detailed info you can find in this Slack thread. Disabling this functionality on the web platform doesn't change anything because emojis styles can be fixed using CSS styles

[Skalakid]

Here is the PR with the fix that removes emoji splitting logic from the web and replaces it with the CSS fix. @shubham1206agra Thank you for the PR, however, there are many more cases where text is duplicated. My PR works around this so we can unblock some PRs and bump the library in the Live Markdown without generating deploy blockers.

Nevertheless, I encourage you to try to fix this issue by changing web parser logic and handling HTML structure building edge cases for situations where we have to split ranges on emojis but there are also styles like bold and inline code block. Here are some desired outcomes:

• _*hello😁world*_ should be rendered in the HTML as _*hello*_😁_*world*_
• _*'inline😁code'*_ should be rendered in the HTML as _*'inline'*_'😁'_*'code'*_ (replace ' with `)

This is something that we will be working on in the future so if only you are interested feel free to submit the PR with the solution :D

[melvin-bot]

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

[melvin-bot]

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

• [CP Staging] Bump react-native-live-markdown version to 0.1.221 #55509

If no regressions arise, payment will be issued on 2025-02-05. 🎊

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

• @sobitneupane requires payment through NewDot Manual Requests
• @Skalakid does not require payment (Contractor)

[melvin-bot]

@sobitneupane @abekkala @sobitneupane The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

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

• [CP Staging] Bump react-native-live-markdown version to 0.1.221 #55509

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

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

• @sobitneupane requires payment through NewDot Manual Requests
• @Skalakid does not require payment (Contractor)

[melvin-bot]

@sobitneupane @abekkala @sobitneupane The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[abekkala]

PAYMENT SUMMARY FOR FEB 06

• Fix: @Skalakid - not payment needed (contractor)
• PR Review: @sobitneupane [$250, if no regressions] payment via NewDot
  Please complete the checklist above.

[melvin-bot]

Payment Summary

Upwork Job

• Reviewer: @sobitneupane owed $250 via NewDot
• Contributor: @Skalakid is from an agency-contributor and not due payment

BugZero Checklist (@abekkala)

• I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1881676503226665257/hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[abekkala]

@sobitneupane can you complete checklist please?

[melvin-bot]

@abekkala, @sobitneupane, @grgia, @Skalakid Whoops! This issue is 2 days overdue. Let's get this updated quick!

[sobitneupane]

Regression Test Proposal

1. Open any chat.
2. To the text that contains emojis, add italics styling, e.g. _🥰 test 😇 test 🥹_
3. Verify if the text has italics style and emojis don't
4. Verify if it still works when adding other styles around it, e.g. # *~_🥰 test 😇 test 🥹_~*
5. Verify if emojis aren't strikethrough

Do we agree 👍 or 👎

[sobitneupane]

BugZero Checklist:

• [Contributor] Classify the bug:

Bug classification

Source of bug:

• 1a. Result of the original design (eg. a case wasn't considered)
• 1b. Mistake during implementation
• 1c. Backend bug
• 1z. Other:

Where bug was reported:

• 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
• 2b. Reported on staging (eg. found during regression or PR testing)
• 2d. Reported on a PR
• 2z. Other:

Who reported the bug:

• 3a. Expensify user
• 3b. Expensify employee
• 3c. Contributor
• 3d. QA
• 3z. Other:

• [Contributor] 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: Prevent italic or strikethrough emojis on Android react-native-live-markdown#591

• [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:

• [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

• [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

  Link to issue: https://github.com/Expensify/Expensify/issues/469621

[melvin-bot]

@abekkala, @sobitneupane, @grgia, @Skalakid Huh... This is 4 days overdue. Who can take care of this?

[abekkala]

Thanks for completing the checklist @sobitneupane

PAYMENT SUMMARY

• Fix: @Skalakid (no payment needed)
• PR Review: @sobitneupane [$250] payment via NewDot

[garrettmknight]

$250 approved for @sobitneupane