Has anyone else experienced this?

[bitdessert]

Per Mattermost guidelines, GitHub issues are for bug reports: http://www.mattermost.org/filing-issues/.

For troubleshooting see: http://forum.mattermost.org/.
For feature proposals see: http://www.mattermost.org/feature-requests/

If you've found a bug--something appears unintentional--please follow these steps:

1. Confirm you’re filing a new issue. Search existing tickets in Jira to ensure that the ticket does not already exist.
2. Confirm your issue does not involve security. Otherwise, please see our Responsible Disclosure Policy.
3. File a new issue using the format below. Mattermost will confirm steps to reproduce and file in Jira, or ask for more details if there is trouble reproducing it. If there's already an existing bug in Jira, it will be linked back to the GitHub issue so you can track when it gets fixed.

Summary

An error occurred with RCTEventEmitter.receiveTouchers().

Environment Information

• Device Name: Vary.
• OS Version: Android
• Mattermost App Version: 2.12.0
• Mattermost Server Version: 9.4.2

Steps to reproduce

It's not clear when it happens.

Expected behavior

There should be no errors.

Observed behavior (that appears unintentional)

While using the app, I received the following pop-up warning

The popup saying the home screen is not registered seems to be fixed, but this one is not.

Possible fixes

[amyblais]

Hi @bitdessert, I found a few threads that could potentially help?

• https://stackoverflow.com/questions/54200471/react-native-ios-rcteventemitter-before-javascript-is-loaded
• https://community.mattermost.com/core/pl/64q7y8w85tbmtjycsomq59wf3y

[bitdessert]

Thanks, @amyblais .
I saw what you sent me, but it's not easy to solve. Can you fix this?
And the 'Relaunch' button in the error handling popup doesn't work. The app doesn't 'Relaunch'.

[amyblais]

Are you using the official app from the app store, or are you building the app yourself? Would you have a full screenshot of the errors (the bottom part in your screenshot seems a bit cut-off, so I wasn't sure if there is anything relevant there).

The popup saying the home screen is not registered seems to be fixed, but this one is not.

Do you have more details on what this is referring to?

[larkox]

@bitdessert It would be great to know more about how this happen. Just as sanity check, what Amy already asked. Is this the official Mattermost app downloaded from Google Play, or is it any other version of the app?

Looking into the error message, a few questions come to mind.

• Does this happen after the app has been asleep for a long while? (not completely closed, but in the background)
• Does this happen while you are doing stuff in the app, or shortly after bringing it from the background?
• Have you ever seen this happening after opening the app completely?
• Does following notifications affect this in any way? (only when following notifications, or not related)

[bitdessert]

@amyblais @larkox I built it myself and am using it.
The reproduction path is not accurate. It's hard to track down why it happens. At this point, I can only say that it happens while using the app.

[larkox]

@bitdessert Are you using master, or an specific release code? Have you made any changes? Is there any chance your changes may be creating this?

[bitdessert]

@larkox I can't say for sure that the code I changed is causing this issue. However, the code I changed is UI related. So it's hard for me to trace it now.