Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Getting the following error - Attempted to transition from state `RESPONDER_INACTIVE_PRESS_IN` to `RESPONDER_ACTIVE_LONG_PRESS_IN`, which is not supported. This is most likely due to `Touchable.longPressDelayTimeout` not being cancelled.
See original GitHub issueI’m getting the following error
Attempted to transition from state RESPONDER_INACTIVE_PRESS_INtoRESPONDER_ACTIVE_LONG_PRESS_IN, which is not supported. This is most likely due to Touchable.longPressDelayTimeout not being cancelled.
I’m on the latest version
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
React Native TouchableNativeFeedback - Stack Overflow
My experience is that the two clocks do not need to be exact match, just make sure they are not off by more...
Read more >Developers - Attempted to transition from state ... - Bountysource
This is most likely due to `Touchable.longPressDelayTimeout` not being cancelled. stack: reactConsoleError @ ExceptionsManager.js:76 ...
Read more >TouchableWithoutFeedback - React Native
onPress . Called when the touch is released, but not if cancelled (e.g. by a scroll that steals the responder lock). The first...
Read more >react-native奇怪报错RESPONDER_INACTIVE_PRESS_IN` to ...
... to `RESPONDER_ACTIVE_LONG_PRESS_IN`, which is not supported. This is most likely due to `Touchable.longPressDelayTimeout` not being ...
Read more >React Native 填坑之神奇的报错，已解决 - 博客园
Attempted to transition from state `RESPONDER_INACTIVE_PRESS_IN` to `RESPONDER_ACTIVE_LONG_PRESS_IN`, which is not supported. This is most ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It seems that this is a React Native problem rather than a react-native-action-button problem, and apparently it’s related to debugging with chrome, otherwise it doesn’t occur, according to this RN issue: https://github.com/facebook/react-native/issues/1693
Yes, after disable debugging it is working fine. It is a react native issue.