Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash with 'InputEventReceiver: Exception dispatching input event' on android N(7.0) #11927

Closed
LittoCats opened this issue Jan 16, 2017 · 9 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@LittoCats
Copy link

Description

My app crash when tap or move in from the left/right edge of screen, and I just recieve adb message as flows:

InputEventReceiver: Exception dispatching input event

crash with empty project too.

RN version: 0.40
Android version: 7.0
Device: HUWEI Mate 9

@sidbusy
Copy link

sidbusy commented Jan 23, 2017

I met the same problem.
Devices: HUAWEI Mate 9 (Android 7.0) & HUAWEI Mate 8 (Android 7.0)

@sidbusy
Copy link

sidbusy commented Jan 23, 2017

Maybe all HUAWEI devices (Android 7.0) have the same problem.

@pinkelf
Copy link

pinkelf commented Jan 24, 2017

Is this the same problem as #11302 ?

@sidbusy
Copy link

sidbusy commented Jan 24, 2017

@pinkelf Is not the same problem.

@sunxfancy
Copy link

sunxfancy commented Feb 26, 2017

Same problem on HUAWEI Mate 8 (Android 7.0) ReactNative 0.38.0

@danielang
Copy link

danielang commented May 4, 2017

Same problem on Huawei P9 (Android 7.0) with React-Native: 0.42.3

Edit:
The problem was fixed for me with the latest RN release.

@pppluto
Copy link

pppluto commented Jun 9, 2017

+1 at mate 8 , android 7
react native: 0.43.1
logcat E InputEventReceiver: Exception dispatching input event.
@danielang which RN version are you use to fix this issue?

@pppluto
Copy link

pppluto commented Jun 9, 2017

@hramos hramos added the Icebox label Aug 16, 2017
@hramos
Copy link
Contributor

hramos commented Aug 16, 2017

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hramos hramos closed this as completed Aug 16, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Aug 16, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Aug 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

9 participants