[$250] Android - Mark down - App crashes when deleting text with mark down in a sentence with heading

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.17-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: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• Device keyboard must be Samsung keyboard
• Issue is not reproducible with Gboard

1. Launch New Expensify app
2. Go to chat
3. Type # hey hey
4. Double tap to select and highlight the second word with mark down _ hey _
5. Tap delete on Samsung keyboard

Expected Result:

App will not crash

Actual Result:

App crashes
This issue is only reproducible with Samsung keyboard and not Gboard

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6563572_1722962062565.Screen_Recording_20240807_002944_Device_care.mp4

logs (2).txt

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01bc8d3436a587add7
• Upwork Job ID: 1821616561702134137
• Last Price Increase: 2024-08-29
• Automatic offers:
• alitoshmatov | Reviewer | 103818157
• wildan-m | Contributor | 103818158

Issue Owner

Current Issue Owner: @isabelastisser

[melvin-bot]

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

[lanitochka17]

We think that this bug might be related to #Live Markdown

[lanitochka17]

@isabelastisser 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

[melvin-bot]

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

[melvin-bot]

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

[BartoszGrajdek]

cc @tomekzaw 👀

[isabelastisser]

No proposals yet.

[melvin-bot]

@isabelastisser, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@isabelastisser, @alitoshmatov Huh... This is 4 days overdue. Who can take care of this?

[isabelastisser]

Still waiting for proposals.

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@isabelastisser, @alitoshmatov 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[alitoshmatov]

Waiting for proposals

[melvin-bot]

@isabelastisser @alitoshmatov 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!

[melvin-bot]

@isabelastisser, @alitoshmatov Whoops! This issue is 2 days overdue. Let's get this updated quick!

[isabelastisser]

No proposals yet.

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[isabelastisser]

@alitoshmatov @wildan-m, can you please provide an update? Thanks!

[wildan-m]

@isabelastisser discussing optimal approach to avoid duplicate calls in upstream. Expensify/react-native-live-markdown#469 (comment)

[tomekzaw]

Expensify/react-native-live-markdown#469 has just been merged

[wildan-m]

Thank you, @tomekzaw!

@alitoshmatov @neil-marcellini Should we simply update the version in the E/App to apply it? I see that the live markdown version in E/App is not the latest. Are there specific steps to follow?

[tomekzaw]

There's already a PR that bumps react-native-live-markdown here: #48626

[wildan-m]

@tomekzaw can we bump the version to 0.1.140 there or we should temporarily create patch until that PR closed?

[tomekzaw]

Let's avoid patches and bump directly to latest if possible

[melvin-bot]

@wildan-m, @neil-marcellini, @isabelastisser, @alitoshmatov 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[tomekzaw]

Should be fixed with #48626

[alitoshmatov]

Waiting for react-native-live-markdown bump on #48626

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[melvin-bot]

@wildan-m, @neil-marcellini, @isabelastisser, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[wildan-m]

Not overdue, The fix PR passed the test and is now live in production #48626 (comment).

[alitoshmatov]

Not overdue.

FYI: I was only involved on selecting proposal, I was not involved in reviewing corresponding PRs

[neil-marcellini]

What's the next step here? What are we waiting for?

[alitoshmatov]

We are in a regression period now. Solution went into production on 16th september

[isabelastisser]

@alitoshmatov, it looks like payment automation failed. I see that it went into production three days ago. Is this ready for payment now? Do we need a regression test? Thanks!

[isabelastisser]

@neil-marcellini @alitoshmatov, it looks like this is ready for payment. Do we need a regression test?

[isabelastisser]

The payments were processed in Upwork. All set!