Attempted to transition from state `RESPONDER_INACTIVE_PRESS_IN` to `RESPONDER_ACTIVE_LONG_PRESS_IN`, which is not supported. #11989

magrinj · 2017-01-19T14:49:42Z

Same as #5823 that has been closed, when I'm in debugging mode with react-native@0.36.1 I got sometimes this error randomly:

console.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."
Object.console.error
    YellowBox.js:61
Constructor._handleLongDelay
    Touchable.js:595
Constructor.proxiedMethod [as _handleLongDelay]
    createPrototypeProxy.js:44
<unknown>
    JSTimers.js:78
Object.callTimer
    JSTimersExecution.js:99
Object.callTimers
    JSTimersExecution.js:140
MessageQueue.__callFunction
    MessageQueue.js:236
<unknown>
    MessageQueue.js:108
guard
    MessageQueue.js:46
MessageQueue.callFunctionReturnFlushedQueue
    MessageQueue.js:107
message
    RNDebuggerWorker.js:123:57

Apparently, thanks to #5823 the code can be reproduced like that:

class App extends Component {
  constructor() {
    super()
    this.state = {
      testText: ''+Math.random()
    }
  }

  _updateTouch(e) {
    this.setState({testText: ''+Math.random()})
  }

  render() {
    return (
      <View style={styles.container}>
        <Text>
          {this.state.testText}
        </Text>
        <TouchableHighlight onPress={this._updateTouch.bind(this)}>
          <Image
            style={width: 100, height: 100}
            source={{uri: 'http://facebook.github.io/react/img/logo_og.png'}}
          />
        </TouchableHighlight>
      </View>
    );
  }
}

I see a lot of people having the same issue on the old ticket, so I choose to open a new one because the old one is actually closed.

The text was updated successfully, but these errors were encountered:

fungilation · 2017-01-25T22:18:08Z

My console.error output:

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

I'm on RN 0.37. I haven't hit this error in iOS simulator, but got this on physical iPhone 6S on iOS 10.2.1.

cparjaszewski · 2017-02-02T17:38:05Z

Same issue here

jsers · 2017-02-09T02:40:35Z

+1
iPhone 6 on iOS 10.2

jose920405 · 2017-02-16T15:59:43Z

+1

rodperottoni · 2017-02-19T23:34:23Z

+1

sebastian-palma · 2017-02-20T13:10:48Z

This only happens to me when Remote JS Debugging is enabled, at least on Android 6, RN v0.41.2.

arkhwise · 2017-02-27T09:21:13Z

react-native: "0.40.0"

I faced with this issue when the following conditions:

Remote JS debugging is on
View has two components, one of them is conditional

<View style={styles.btnWrapper}>
  <TextButton
    title='text'
    onPress={this.foo}
  />
  {
   this.props.enableHint &&
   <TextButton
    title='text'
    onPress={this.bar}
   />
  }
</View>

// TextButton
<TouchableHighlight
  onPress={this.props.onPress}
>
  <Text>
    {this.props.title}
  </Text>
</TouchableHighlight>

When enableHint is eq false, RN throws this error

I change <TouchableHighlight> to <TouchableOpacity> and that's works.

langjun · 2017-05-12T06:59:33Z

+1

Android 7.1.1
Nexus 6

ddellamico · 2017-05-12T13:31:55Z

+1

devken-net · 2017-05-15T00:42:20Z

+1

jasonmerino · 2017-05-16T15:47:58Z

I am also getting this error when remote JS debugging is on my Android device. RN v0.42.3

spencewine · 2017-05-18T18:19:54Z

+1 RN 0.42.0

sporteman · 2017-05-30T00:48:21Z

+1 RN 0.44

ank-khandelwal · 2017-06-22T06:56:00Z

+1 RN 0.44.2

half-shell · 2017-06-28T11:04:30Z

+1 RN 0.45.1
I'm really sorry to keep the spam going, but it's been bothering be for a while now, and I think it is the reason my apps closes itself now and then.

I'd be happy to provide any useful information in order to solve this issue.

jonathanroze · 2017-06-28T15:56:51Z

+1

bgoyal2222 · 2017-06-30T10:37:06Z

+1 RN 0.43.4

Larry-Liu2016 · 2017-07-10T13:50:48Z

Hey everyone. Just check the clocks on your computer and phone. If there is a noticeable difference, disable the auto setting on one device and change it to match the other.

My android phone's clock was around 7s earlier than the clock on my Mac, and there was ~ 1/3 chance to trigger the error when button is pressed with chrome debugging on. After I adjust the clock to reduce the difference to around 1s (without changing any code), the problem is gone.

fungilation · 2017-07-10T22:35:25Z

Does Android not use internet time servers properly to have a 7s discrepancy? 🤔

On Mon, Jul 10, 2017 at 6:52 AM Larry-Liu2016 ***@***.***> wrote: Hey everyone. Just check the clocks on your computer and phone. If there is a noticeable difference, disable the auto setting on one device and change it to match the other. My android phone's clock was around 7s earlier than the clock on my Mac, and there was ~ 1/3 chance to trigger the error when button is pressed with chrome debugging on. After I adjust the clock to reduce the difference to around 1s (without changing any code), the problem is gone. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#11989 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADoJStomJi_3OHaNf8iN5NkooI3HBgnzks5sMiyYgaJpZM4LoMao> .

-- Cheers, Gary

yash2code · 2017-07-22T05:53:08Z

+1

MrToph · 2017-07-22T14:39:19Z

+1

ghulamMustafaRaza · 2017-07-28T14:31:48Z

+1

fungilation · 2017-07-28T18:59:28Z

STOP with the +1 spam. Just give the original post or whichever comment a thumbs up 👍🏼 if you see the same.

compojoom · 2017-09-06T08:29:01Z

I just did what @Larry-Liu2016 suggested and this worked for me on RN 0.47.2
This also seems to solve the onlongpress issue reported here: #4944

Thanks @Larry-Liu2016

Ariel08081214 · 2017-09-17T00:40:02Z

RN 0.48.2 +1
How is this question triggered?
What is the solution？

compojoom · 2017-09-17T11:44:56Z

@danna88 try to set the phone's time manually and make sure it's equal to the computer time. Then let us know if you still experience the issue.

michelebombardi · 2017-09-23T08:38:43Z

+1 RN 0.48.3

hassanjallow · 2017-10-16T00:49:56Z

@Larry-Liu2016 suggestion worked for me on RN 0.46.4. Thanks

koansang · 2017-10-17T13:10:59Z

+1 RN 0.49.3 on Android

syzer · 2017-10-18T13:27:14Z

+1 on Android

DevCappe · 2017-10-19T13:38:51Z

+1

mhdizade · 2017-10-21T09:15:47Z

+1

gino8080 · 2017-11-06T15:30:42Z

Solved using React Native debugger instead of plain Chrome window

tasneembohra · 2017-11-08T10:30:12Z

@Larry-Liu2016 +1

jetonk · 2017-11-30T13:17:56Z

@Larry-Liu2016 is right, I have synchronized time to my android mobile phone with the computers time, exactly the same even the seconds, and now that error does not appear.

alanyong91 · 2017-12-18T14:37:20Z

We solutions over here. Stop comment +1. Not just here. In every post, please don't comment "me too" and "+1". Thanks for the cooperation

sneerin · 2017-12-29T14:56:03Z

the solution to fix the clock is not an option, you can't say every customer to fix their time.

jetonk · 2017-12-29T20:14:44Z

@sneerin This issue it is just in development mode, not in production..

SkyzohKey · 2018-01-16T13:03:59Z

@jetonk Still pretty boring when you develop and your app crash cuz of that shit. e.e

DarkHollow · 2018-01-23T06:50:19Z

Time synchronized and not working...
I have also tried inserting View inside TouchableNativeFeedback with the same result.

mohammad-goldast · 2018-02-11T09:05:21Z

Android 7 & RN 0.53

I've same issue with TouchableHighlight

RobTS · 2018-02-21T09:59:24Z

Time synchronized, not working here either...

Piropa · 2018-02-23T15:09:00Z

My practical solution was to edit react-native source code at:
node-modules/react-native/Libraries/Components/Touchable/Touchable.js

Here I've changed "console.error" to "console.log" at line 628, this way I receive the message, however my app is not interrupted and the error is "dissmissed"

You could also use "console.warn" if you still want to get track of the error, turning it into a warning.

starting at line 623:

  _handleLongDelay: function(e) {
    this.longPressDelayTimeout = null;
    var curState = this.state.touchable.touchState;
    if (curState !== States.RESPONDER_ACTIVE_PRESS_IN &&
        curState !== States.RESPONDER_ACTIVE_LONG_PRESS_IN) {
      // console.error('Attempted to transition from state `' + curState + '` to `' +
      console.log('Attempted to transition from state `' + curState + '` to `' +
        States.RESPONDER_ACTIVE_LONG_PRESS_IN + '`, which is not supported. This is ' +
        'most likely due to `Touchable.longPressDelayTimeout` not being cancelled.');
    } else {
      this._receiveSignal(Signals.LONG_PRESS_DETECTED, e);
    }
  },

react-native-bot · 2018-02-24T03:27:33Z

Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

_{How to Contribute • What to Expect from Maintainers}

pacozaa · 2018-03-10T02:38:39Z

@Piropa Thank you. +1

hramos · 2018-04-04T21:39:58Z

Locking due to repetitive +1 comments. A solution was posted a long time ago by @Larry-Liu2016 here. In summary, check the clock on your devices.

magrinj mentioned this issue Jan 19, 2017

Attempted to transition from state RESPONDER_INACTIVE_PRESS_IN to RESPONDER_ACTIVE_LONG_PRESS_IN, which is not supported. #5823

Closed

react-native-bot added Ran Commands One of our bots successfully processed a command. Stale There has been a lack of activity on this issue and it may be closed soon. labels Feb 24, 2018

react-native-bot closed this as completed Feb 24, 2018

stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 24, 2018

dannycochran mentioned this issue Mar 26, 2018

don't crash app from _handleLongDelay #18573

Closed

facebook locked as resolved and limited conversation to collaborators Apr 4, 2018

react-native-bot added the Resolution: Locked This issue was locked by the bot. label Dec 11, 2019

Attempted to transition from state RESPONDER_INACTIVE_PRESS_IN to RESPONDER_ACTIVE_LONG_PRESS_IN, which is not supported. #11989

Attempted to transition from state RESPONDER_INACTIVE_PRESS_IN to RESPONDER_ACTIVE_LONG_PRESS_IN, which is not supported. #11989

Comments

magrinj commented Jan 19, 2017

fungilation commented Jan 25, 2017 • edited Loading

cparjaszewski commented Feb 2, 2017

jsers commented Feb 9, 2017 • edited Loading

jose920405 commented Feb 16, 2017

rodperottoni commented Feb 19, 2017

sebastian-palma commented Feb 20, 2017

arkhwise commented Feb 27, 2017 • edited Loading

langjun commented May 12, 2017 • edited Loading

ddellamico commented May 12, 2017

devken-net commented May 15, 2017

jasonmerino commented May 16, 2017

spencewine commented May 18, 2017

sporteman commented May 30, 2017

ank-khandelwal commented Jun 22, 2017

half-shell commented Jun 28, 2017

jonathanroze commented Jun 28, 2017

bgoyal2222 commented Jun 30, 2017

Larry-Liu2016 commented Jul 10, 2017

fungilation commented Jul 10, 2017 via email

yash2code commented Jul 22, 2017

MrToph commented Jul 22, 2017

ghulamMustafaRaza commented Jul 28, 2017

fungilation commented Jul 28, 2017

compojoom commented Sep 6, 2017

Ariel08081214 commented Sep 17, 2017

compojoom commented Sep 17, 2017

michelebombardi commented Sep 23, 2017

hassanjallow commented Oct 16, 2017

koansang commented Oct 17, 2017

syzer commented Oct 18, 2017

DevCappe commented Oct 19, 2017

mhdizade commented Oct 21, 2017

gino8080 commented Nov 6, 2017

tasneembohra commented Nov 8, 2017

jetonk commented Nov 30, 2017

alanyong91 commented Dec 18, 2017

sneerin commented Dec 29, 2017

jetonk commented Dec 29, 2017 • edited Loading

SkyzohKey commented Jan 16, 2018

DarkHollow commented Jan 23, 2018

mohammad-goldast commented Feb 11, 2018

RobTS commented Feb 21, 2018

Piropa commented Feb 23, 2018 • edited Loading

react-native-bot commented Feb 24, 2018

pacozaa commented Mar 10, 2018

hramos commented Apr 4, 2018 • edited Loading

Attempted to transition from state `RESPONDER_INACTIVE_PRESS_IN` to `RESPONDER_ACTIVE_LONG_PRESS_IN`, which is not supported. #11989

Attempted to transition from state `RESPONDER_INACTIVE_PRESS_IN` to `RESPONDER_ACTIVE_LONG_PRESS_IN`, which is not supported. #11989

fungilation commented Jan 25, 2017 •

edited

Loading

jsers commented Feb 9, 2017 •

edited

Loading

arkhwise commented Feb 27, 2017 •

edited

Loading

langjun commented May 12, 2017 •

edited

Loading

jetonk commented Dec 29, 2017 •

edited

Loading

Piropa commented Feb 23, 2018 •

edited

Loading

hramos commented Apr 4, 2018 •

edited

Loading