react-native: onLongPress (and delayLongPress) triggers immediately

For some reason (I have no clue why) onLongPress triggers immediately, and onPress doesn’t. tested on : android simulator with genymotion (galaxy5) and real galaxy3 device

After adding delayLongPress i figured out that it’s “stealing” 1000ms from the delay, and I guess the default delay is 1000, so it’s triggering immediately.

for example :

  <TouchableOpacity      
               delayLongPress={3800}
               onPress={()=>{
                  console.log(' onPress');  
                  console.log(Date.now())}}
               onPressIn ={()=>{
                  console.log('TouchableOpacity onPressIn'); 
                  console.log(Date.now())
                }}
               onLongPress ={(e)=>{
                  console.log(' onLongPress');
                  console.log(Date.now());
                  console.log(e.type); //undefined
               }}
           >

when I calculate : onLongPress time - onPressIn time , I get ~2800ms without delayLongPress or with delayLongPress={1000} I get 10-20ms

About this issue

Original URL
State: closed
Created 9 years ago
Reactions: 9
Comments: 34 (6 by maintainers)

Most upvoted comments

Same. Confirming that this happens only with chrome debugger enabled.

nicastelo on Aug 8, 2016

This breaks only when debug JS remotely is enabled. im using VSCode debugger. this needs to be reopened

ghost on Feb 26, 2018

Still having this issue and only happen when connected to Chrome debugger.

gorvinsky on Feb 6, 2018

+1 happening only with chrome debugger. I hope this doesn’t happens in production.

themakerman on Oct 3, 2017

Hmm it randomly started happening, after testing on real device with RN Debugger. it was working fine, and suddenly stopped working, onLongPress is being called on quick single tap instead of onPress.

pocesar on Feb 27, 2017

ExceptionsManager.js:71 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 @ ExceptionsManager.js:71console.error @ YellowBox.js:61_handleLongDelay @ Touchable.js:596proxiedMethod @ createPrototypeProxy.js:44(anonymous function) @ JSTimers.js:80callTimer @ JSTimersExecution.js:95callTimers @ JSTimersExecution.js:136__callFunction @ MessageQueue.js:236(anonymous function) @ MessageQueue.js:108guard @ MessageQueue.js:46callFunctionReturnFlushedQueue @ MessageQueue.js:107onmessage @ debuggerWorker.js:44

zyxcambridge on Dec 14, 2016

Confirmed… this is still happening. Only when dev tools is connected tho.

digitalmaster on Sep 3, 2017

Looks like the same problem, closed dev-tools (and added other display - not console.log) and it’s working fine

yonatanmn on Dec 23, 2015

forgive

whylifes on Oct 18, 2017

hello,I am go away!

whylifes on Oct 18, 2017

A competition

whylifes on Oct 18, 2017

it’s been inactive but still happening and should not be closed. it’s even worse lately when using react-native-router-flux because it brings up a red box when transitioning between scenes with the error mentioned by @zyxcambridge

pocesar on Jul 21, 2017

Yes still happening… (i am on ios) Was working fine yesterday and today bam…

Athosone on Sep 3, 2017

Confirming that this happens only with chrome debugger enabled.

christopherdro on May 12, 2016

Duplicate of this? #4088

satya164 on Dec 23, 2015