[$500] Entering certain diacritics such as à, á, â in the composer is broken (iOS Simulator)

[m-natarajan]

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: 1.4.39-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
Expensify/Expensify Issue URL:
Issue reported by: @francoisl
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1707435603099939

Action Performed:

1. Open any chat
2. In the composer, type Option+`, then a

Expected result:

à is entered in the composer

Actual result:

`a is entered in the chat
Same goes with Option+e , then letter, e.g. ´a is entered instead of á

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

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~011af575af2fe9ca45
• Upwork Job ID: 1755783765816233984
• Last Price Increase: 2024-02-16

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~011af575af2fe9ca45

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @greg-schroeder (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[ikevin127]

👋 As a native romanian I can confirm that these diacritic characters work if pasted / written directly in the composer using native keyboard (or native keyboard shortcut extensions):

I never encountered any apps in which I had to write a certain combination of characters which then were parsed to my native diacritics like: ă, â, î, ș, ț, french ones like à, è, ù, or german ones: ä, ö, ü, ß.

If we're expecting character combinations like ´a to be parsed as á then I think that would be a new feature, though a pretty confusing one 👀 since there are so many language diacritics that would have to come up w/ character combinations for.

Unless this used to work at a certain point (by design) and it doesn't work anymore.

[francoisl]

written directly in the composer using native keyboard

Ah yes I think that's the difference, I'm using a Macbook with a US English keyboard, which doesn't have any keys with accents.

To clarify, this is not an Expensify-specific feature, it's a native way to enter accents on MacOS, and so far I haven't seen any app where this didn't work.

The other way is to long-press on a key like a, and it opens a small modal with the variations of the letter you can choose from, but I don't think anyone in their right mind uses that regularly 😄

[francoisl]

Btw, forgot to mention but this is most likely due to #35837.

[jeremy-croff]

Btw, forgot to mention but this is most likely due to #35837.

Cannot reproduce anymore, I believe that was the culprit and had been reverted.

[tomekzaw]

A similar issue also occurs on iOS simulator. The diacritics are correctly applied but the leading backtick is not removed.

Using RNTextInput (without Live Markdown Preview):

RNTextInput.mov

Using MarkdownTextInput (with Live Markdown Preview):

MarkdownTextInput.mov

[tomekzaw]

This issue is reproducible in Live Markdown example app, reported as Expensify/react-native-live-markdown#181.

[melvin-bot]

@sobitneupane, @greg-schroeder Whoops! This issue is 2 days overdue. Let's get this updated quick!

[greg-schroeder]

Okay - should we create a new issue or just change this one to focus on the iOS case?

[tomekzaw]

The behavior on native iOS will be fixed in Expensify/react-native-live-markdown#182.

[francoisl]

@tomekzaw to clarify, will that PR only fix native iOS? Cause the issue was also happening on web & desktop. Either way it's fine, we can keep this issue open to remember to also fix other platforms.

[tomekzaw]

@francoisl That's correct, this PR only fixes native iOS. We're still investigating the issue on web.

[greg-schroeder]

Cause the issue was also happening on web & desktop. Either way it's fine, we can keep this issue open to remember to also fix other platforms.

All right - but I thought web was fixed by the revert of #35837? @francoisl

[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]

@sobitneupane, @greg-schroeder Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@tomekzaw @greg-schroeder @thienlnam this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

[melvin-bot]

@tomekzaw, @greg-schroeder, @thienlnam Whoops! This issue is 2 days overdue. Let's get this updated quick!

[greg-schroeder]

Thoughts on a timeline for this one @tomekzaw? Just want to make sure I'm on the same page <3

[tomekzaw]

@greg-schroeder Since this issue happens only on iOS simulators, we decided to deprioritize this and focus on the analogous issue happening on web first. Once we fix it for web, I will continue working on this issue.

[melvin-bot]

@tomekzaw, @greg-schroeder, @thienlnam Whoops! This issue is 2 days overdue. Let's get this updated quick!

[thienlnam]

Updating the priority - this does not impact any real devices

[melvin-bot]

@tomekzaw @greg-schroeder @thienlnam this issue is now 4 weeks old and preventing us from maintaining WAQ, can you:

• Decide whether any proposals currently meet our guidelines and can be approved as-is today
• If no proposals meet that standard, please take this issue internal and treat it as one of your highest priorities
• If you have any questions, don't hesitate to start a discussion in #expensify-open-source

Thanks!

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @abdulrahuman5196 (Internal)

[melvin-bot]

@tomekzaw, @greg-schroeder, @thienlnam, @abdulrahuman5196 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[greg-schroeder]

Closing this per team discussion