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

[magrinj]

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.

[fungilation]

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]

Same issue here

[jsers]

+1
iPhone 6 on iOS 10.2

[jose920405]

+1

[rodperottoni]

+1

[sebastian-palma]

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

[arkhwise]

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]

+1

Android 7.1.1
Nexus 6

[ddellamico]

+1

[devken-net]

+1

[jasonmerino]

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

[spencewine]

+1 RN 0.42.0

[sporteman]

+1 RN 0.44

[ank-khandelwal]

+1 RN 0.44.2