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

[samhunta]

Similar to #1693. It seems to be an issue with the Touchable component with Chrome Debugging on React Native 0.19.0.

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.

stack:
reactConsoleError                                 @ ExceptionsManager.js:76
console.error                                     @ YellowBox.js:49
TouchableMixin._handleLongDelay                   @ Touchable.js:575
JSTimersExecution.callbacks.(anonymous function)  @ JSTimers.js:47
JSTimersExecution.callTimer                       @ JSTimersExecution.js:69
JSTimersExecution.callTimers                      @ JSTimersExecution.js:92
__callFunction                                    @ MessageQueue.js:183
(anonymous function)                              @ MessageQueue.js:87
guard                                             @ MessageQueue.js:41
callFunctionReturnFlushedQueue                    @ MessageQueue.js:86
onmessage                                         @ debuggerWorker.js:39

The code that produces this error is from a freshly started application using a TouchHighlight component:

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>
    );
  }
}

P.S. Is there a better way to copy a stacktrace? I'm just copying from the Chrome dev tools console

[facebook-github-bot]

Hey Dyscrete, thanks for reporting this issue!

React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.

• If you don't know how to do something or something is not working as you expect but not sure it's a bug, please ask on StackOverflow with the tag react-native or for more real time interactions, ask on Discord in the #react-native channel.
• If this is a feature request or a bug that you would like to be fixed, please report it on Product Pains. It has a ranking feature that lets us focus on the most important issues the community is experiencing.
• We welcome clear issues and PRs that are ready for in-depth discussion. Please provide screenshots where appropriate and always mention the version of React Native you're using. Thank you for your contributions!

[casperin]

I get the same error when testing on an iPhone6 (9.1)

[grabbou]

How's this issue different from #1693 ? In general, the issue seems to be the same. Can we close it and continue further investigation up there as it has more details?

[askday]

+1
I also get this problem,and It's happened frequently switch navigator

[grabbou]

Going to close it as @askday also put better repro in the #1693. Please reopen if OP mentioned something different.

[radek1991]

Same error for me.
React 0.31
Chrome debug.
In normal use there is no problem.

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:60
Constructor._handleLongDelay
Touchable.js:595
JSTimersExecution.callbacks.(anonymous
index.ios.bundle?platform=ios&dev=true&minify=false:8476:13
Object.callTimer
JSTimersExecution.js:84

JSTimersExecution.js:119
Object.callTimers
JSTimersExecution.js:119
MessageQueue.__callFunction
MessageQueue.js:204

MessageQueue.js:95

[stief510]

+1

[charlesLin]

+1

[pawellewandowski]

+1

[minhchu]

+1

[gillestasse]

👍

[Jarred-Sumner]

👍

[StevenKing9]

+1

[bucketclan]

+1

[myseven]

+1

[SerzN1]

+1

[johnwei2019]

+1

[berkaybeyaz1]

+1

[dadbob]

+1

[nadeermalangadan]

+1

[ouabing]

+1

[nikolal]

I am also having this error, but only on Android. IOS is working as expected.

[chandlervdw]

+1

[helloncanella]

+1

[Yangzhedi]

+1

[wasa4587]

+1

[pyshchyk-o]

+1

[haloJim]

+1

[toearth]

+1 for 0.48.3

[JaEdmuva]

+1 on 0.51.0

[Fortidude]

+1 is nice, love it. Happens of 0.50

[TimorYang]

+1

[giovanniRodighiero]

+1

[iotdog]

+1

with react-native 0.51.0

[basbase]

I 'fixed' this by manually setting the device time in Android. Make sure the new time will equal that of your computer (aim for the next minute change), confirm the time change on the very same second your computer time will change to the next minute.

[roshanpal]

+1

[MedinaGitHub]

+1

[sizovilya]

+1

[anwarhamr]

+1

[vvavepacket]

+1

[xemasiv]

Solution to me was to

1. Ensure phone and pc got same timezone
2. Manually update time on pc: Date and Time -> Internet Time tab -> Change Settings -> Update Time
3. Toggle-on auto time update in android settings, then toggle it off
4. Restart the app

[sandrojurado]

In Libraries\Components\Touchable\TouchableHighlight.js replace

touchableGetLongPressDelayMS: function() {
return this.props.delayLongPress;
},

with

touchableGetLongPressDelayMS: function() {
return this.props.delayLongPress === 0 ? 0 :
this.props.delayLongPress || 500;
},

It resolved the problem for me.

[brzonsea]

+1

[b45ch1]

I had the same issue on Android when
a) my mobile phone was connected to my PC via USB
b) I used remote debugging via network

Disconnecting USB resolved the issue. No idea if there is a causal relationship, though.

Edit: After getting additional issues with async timeouts I checked the current time on PC and Android device via

adb shell date && date.

There was a 5 seconds discrepancy. One might be tempted to guess that there is an inconsistency in how RN handles the current time when debugging remotely.
Via

curl -s --head http://google.com | grep ^Date: | sed 's/Date: //g'

I pinned down the culprit in my case: the system time of my Android device was off by 5 seconds. Rebooting the Android device fixed the discrepancy.

[Benzer1406]

I just verified the time from the Android device and my Mac with : adb shell date && date. It was differing by more than 2 minutes. Then I activated the automatic time setting on my Android device and ran the same command again and voilá the time was syncronized, but the time zone was not the same even though on both (Android device and Mac) the time zone setting was automatic. So I deactivated the automatic time zone setting on my Android device and set it manually to the corresponding and the error disappeared.

[abaddonGIT]

+1

[guitar9]

automatic time setting on android device and automatic time setting on computer solved the problem

[remigarcia]

on Ubuntu I synchronized system time with the current ADB time by doing :

sudo date +%T -s `adb shell date +%T`

[hramos]

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.