An error occurred while using TouchableHighlight，can you help me?

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

Steps to Reproduce

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.

| reactConsoleErrorHandler | @ | A:\CricketClient\nod…ptionsManager.js:71 | console.error | @ | A:\CricketClient\nod…ive\YellowBox.js:62 | _handleLongDelay | @ | A:\CricketClient\nod…le\Touchable.js:628 | proxiedMethod | @ | A:\CricketClient\nod…rototypeProxy.js:44 | (anonymous) | @ | A:\CricketClient\nod…mers\JSTimers.js:92 | callTimer | @ | A:\CricketClient\nod…mersExecution.js:95 | callTimers | @ | A:\CricketClient\nod…ersExecution.js:136 | __callFunction | @ | A:\CricketClient\nod…MessageQueue.js:250 | (anonymous) | @ | A:\CricketClient\nod…MessageQueue.js:101 | __guard | @ | A:\CricketClient\nod…MessageQueue.js:218 | callFunctionReturnFlushedQueue | @ | A:\CricketClient\nod…MessageQueue.js:100 | (anonymous) | @ | debuggerWorker.js:71

Expected Behavior

(Write what you thought would happen.)

Actual Behavior

(Write what happened. Add screenshots!)

Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

[christianchown]

I get this a fair bit, running on Android on a real device… but it only occurs after I have Hot Reloaded at least once.

If that’s the case for you, @Vagrant-gb, it’s safe to ignore. Just dismiss the warning dialog and continue working. I found a thread describing the reason why it occurs. I can’t remember exactly what it was, but it’s a non-issue.

[stale[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. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.