Status-react: Error calling RCTEventEmitter.receiveEvent when tap on emoji from predictive text panel

[Serhy]

Type: Bug

Summary: java.lang.RuntimeException: Error calling RCTEventEmitter.receiveEvent error followed by the app crash appear when contact taps the emoji from auto-correction suggestions. Note - it should be a single emoji in auto-correction, it's all OK for text+emoji

Expected behavior

No errors when contact taps the emoji from auto-correction suggestions. Emoji appears in message box

Actual behavior

java.lang.RuntimeException: Error calling RCTEventEmitter.receiveEvent error followed by the app crash appears when contact taps upon emoji from auto-correction suggestions

Precondition

You may need to create auto replacement for text by emoji on Android if you don't have any.
For Android 6, for example, it could be done navigating to device Settings -> Language and input -> Keyboards -> Text shortcuts -> Add and add a text you want to be replace by replacement (e.g. Shortcut='Hello' and Expanded phrase = [Emoji symbol you wish to be replaced by]
Also Predictive text option setting should be turned on on the keyboard.

Reproduction

• Open Status and create an account
• Navigate to any type of chat (e.g. join public chat predictemoji)
• In message box type the text you are about to replace by emoji
• Send the text message (Note: auto replacement area with the emoji keep stay)
• Tap on emoji from predictive text

Additional Information

• Status version: Develop, Release 0.9.17 / 0.9.18
• Operating System: Android

Logs

TF session with logs: https://app.testfairy.com/projects/4803622-status/builds/8227614/sessions/20/?accessToken=pQJq1uPWXf0Ox4ksujA2BAtPwzE

TestFairy: Status 0.9.16-79-gca809264+ (2506) @20

[yenda]

Potatoe bug

(easier to search later)

[yenda]

This is a react-native issue, we have to wait for a fix https://github.com/facebook/react-native/issues/18405

[yenda]

The PR to follow for a fix https://github.com/facebook/react-native/pull/18443

[yenda]

Moved to post-beta as this is unlikely that we can solve this bug before beta since it requires a PR to be merged in react-native and a release of react-native

[status-github-bot[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Serhy]

I can not reproduce this issue anymore!