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

Got DOWN touch before receiving UP or CANCEL from last gesture #30080

Closed
yevhenlv opened this issue Sep 30, 2020 · 19 comments
Closed

Got DOWN touch before receiving UP or CANCEL from last gesture #30080

yevhenlv opened this issue Sep 30, 2020 · 19 comments
Labels
Needs: Author Feedback Needs: Issue Template This issue does not make use of the Issue Template, and may be missing necessary information. Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@yevhenlv
Copy link

yevhenlv commented Sep 30, 2020

Got next error in ReactNative (android)

E unknown:ReactNative: Got DOWN touch before receiving UP or CANCEL from last gesture
PowerWrap: PowerHal_TouchBoost
Screen doesn't react on touch events and looks like freezing, but all background tasks running with success result and debugger doesn't show other errors.

RN 0.63.3 RN-navigation 7.0.0

System:
OS: macOS 10.15.6
CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
Memory: 33.66 MB / 8.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.18.0 - /usr/local/bin/node
Yarn: 1.19.0 - /usr/local/bin/yarn
npm: 6.14.4 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.0. - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
Android SDK: Not Found
IDEs:
Android Studio: 3.5 AI-191.8026.42.35.5791312
Xcode: 12.0/12A7209 - /usr/bin/xcodebuild
Languages:
Java: javac 13 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.3 => 0.63.3
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

@penchef
Copy link

penchef commented Oct 5, 2020

experiencing the same issue ( "react-native": "0.63.2", "react-native-navigation": "^6.7.1", // edited) on android emulator in debug mode only.

@spacesuitdiver
Copy link

@penchef are you using rn-navigation?

@penchef
Copy link

penchef commented Oct 5, 2020

@spacesuitdiver yes "react-native-navigation": "^6.7.1",

UPDATE:

Neither updating to react-native-navigation 6.12.2 nor 7.1.0 solved the issue

@yevhenlv
Copy link
Author

yevhenlv commented Oct 5, 2020

RNN version 7.0
I don't know is it correct, but I found solution on rnn docs:

https://wix.github.io/react-native-navigation/docs/installing

app/build.gradle

dependencies { ... implementation 'com.android.support:design:25.4.0' implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}" }

Adding this two dependencies solved problem.

@spacesuitdiver
Copy link

spacesuitdiver commented Oct 5, 2020

Tried what @yevhenlv suggested, no luck on my end, using RNN 7.1.0.

@penchef
Copy link

penchef commented Oct 5, 2020

ditto: no luck with suggested workaround, tried RNN 7.0.0 / 7.1.0 / 6.7.1 ...

@yevhenlv
Copy link
Author

yevhenlv commented Oct 7, 2020

I think it depends on warnings on screen (after opening one of them I got this error again).

@wanschi
Copy link

wanschi commented Oct 19, 2020

Same issue here

@wanschi
Copy link

wanschi commented Oct 20, 2020

@penchef @spacesuitdiver Did you find a solution?

@Joshuapwilley
Copy link

Chiming in to say I'm experiencing the same issue.

react-native: 0.63.3
react-native-navigation: 7.1.0

Experiencing the error on real device & emulator. Only occurs in debug mode on Android. Release builds do not have this issue.
Also - I am completely unable to use the app at all in debug mode on Android. No touch events register at all.

@safaiyeh safaiyeh added Needs: Issue Template This issue does not make use of the Issue Template, and may be missing necessary information. Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. labels Oct 25, 2020
@github-actions
Copy link

⚠️ Missing Reproducible Example
ℹ️ It looks like your issue is missing a reproducible example. Please provide a Snack or a repository that demonstrates the issue you are reporting in a minimal, complete, and reproducible manner.

@github-actions
Copy link

⚠️ Missing Required Fields
ℹ️ It looks like your issue may be missing some necessary information. GitHub provides an example template whenever a new issue is created. Could you go back and make sure to fill out the template? You may edit this issue, or close it and open a new one.

@safaiyeh
Copy link
Contributor

Is this issue specific to RNN? Could someone provide a small repro of this issue, to debug further?

@Joshuapwilley
Copy link

I am not sure if this issue is related to RN or RNN, but for anyone who comes across this issue without resolution, I can confirm downgrading to the following versions resolved the issue for me:

react-native: 0.61.5
react-native-navigation: 6.7.5

Obviously this solution will not work for those who want to be on RN 0.63+ and RNN 7+, but I couldn't spend the time troubleshooting this issue so the version downgrade was a welcome compromise.

@Frank1234
Copy link

The LogBox Dialog is picking up (part of) the touches. You can see this when you add a breakpoint to View.dispatchTouchEvent at the places where it returns "true": the ReactRootView from LogBox takes the touch.
If you open "LogBoxModule.java" you will see that it creates a ReactRootView, and adds it to a Dialog. This apparently invisible dialog blocks the UI.

The cause: someone is calling "show()" from Javascript, and nothing shows but an empty dialog. I'm done with debugging. Working around the problem for now, by adding my own LogBoxModule implementation, that does not call super.show() and implements canOverrideExistingModule to true. The downside of this is that the app will not show the fullscreen LogBox, only the toasts.

@wanschi
Copy link

wanschi commented Nov 23, 2020

@Frank1234 Could you share some code or some useful links for creating own module implementations? I'm still facing this issue.

@penchef
Copy link

penchef commented Dec 9, 2020

UPDATE

#kudos to @risland for isolating the issue!

We've been able to create a (minimal??) reproducible repo:

As @yevhenlv and @Frank1234 were suspecting, the issue seems to be with some empty error dialog popping up over everything else.

In our case the issue was an Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication) caused by the Navigation.registerComponent call inside the persistStore callback.

Moving the Navigation.registerComponent outside solved the issue (for us).

import {persistStore, persistReducer} from 'redux-persist';
import {Navigation} from 'react-native-navigation';
import {combineReducers, createStore, compose} from 'redux';

import AsyncStorage from '@react-native-community/async-storage';

import React from 'react';
import {SafeAreaView, StatusBar, Button, Alert} from 'react-native';

// DOES WORK HERE!
Navigation.registerComponent('foo.bar', () => App);

const store = configureStore();

persistStore(store, null, () => {
  // DOES NOT WORK HERE!
  // Navigation.registerComponent('foo.bar', () => App);

  Navigation.setRoot({
    root: {
      stack: {
        children: [
          {
            component: {
              name: 'foo.bar',
            },
          },
        ],
      },
    },
  });
});

...

Good luck everyone out there!

@github-actions
Copy link

This issue is waiting for author's feedback since 24 days. Please provide the requested feedback or this will be closed in 7 days.

@github-actions github-actions bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Apr 13, 2023
@github-actions
Copy link

This issue was closed because the author hasn't provided the requested feedback after 7 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Author Feedback Needs: Issue Template This issue does not make use of the Issue Template, and may be missing necessary information. Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

7 participants