React-native: 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]

:+1:

[Jarred-Sumner]

👍

[StevenKing9]

+1

[bucketclan]

+1

[myseven]

+1

[SerzN1]

+1

[johnjichaowei]

+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

[mp31415]

+1

[binzailani3136]

+1 same error only on Android but iOS works fine.

[getnashty]

+1 same as @binzailani3136

[timsawtell]

+1

[Yangzhedi]

恭喜此bug当选 RN0.39版 最臭名昭著的issue之一

[futurechallenger]

+1

[tqqttq]

+1

[banzheshenghuo]

+1

[XinQiXiao]

+1

[lucaschain]

+1

[zlllya]

+1

[bdart]

+1

[BabuinGH]

+1

[braco]

Guys, your +1s aren't helpful, and this is in #1693

[BeckZero]

+1

[a-eid]

+1

[KamWis]

+1

[felipembbraga]

+1

[kylin93]

+1

[UlfR]

+1

[magrinj]

As I see a lot of people seems to always have this issue, and this one is closed, so I create a new one here: #11989

[JumalDB]

+1

[leoabacade]

+1

[fungilation]

@magrinj, why is this issue closed when so many, including I just now on RN 0.37, continue to hit this error? Is there a stopgap fix from the app side?

[magrinj]

@fungilation Maybe I did a mistake by opening a new ticket, because this one is open and talk about the same problem: #1693

[Yadro]

Fixed after add View

<TouchableNativeFeedback>
     <View> // <= here
         <Text style={css.item}>{rowData.title + rowData.id}</Text>
     </View>
</TouchableNativeFeedback>

[fungilation]

@Yadro, you mean inserting additional View fixes this from the app side, or RN can fix it internally by doing so?

[Yadro]

hm, my English is bad, but inserting additional View resolve this problem

[fungilation]

Ok. I'll report back if I still hit this issue with additional Views

[edencakir]

+1

[ckwong90]

I only get this when I'm in remote debugging. This doesn't happen normally. RN .41.2. Windows 10. Android

[jose920405]

+1

[sergchil]

@ckwong90, some here, only apears when remote debugging
RN .41.2. macOS Sierra 10.12.3

[baotoan1905]

• 1 same problem

[volodymyrrudyi]

Same here, Android 6.0, latest RN, remote debugging

[martinjobb]

+1

[whyming]

+1

[xingjianpan]

+1

I encounter this problem with react-native-button and debug model in Chrome

I solved the issue by wrapping the Button component with View.

[Rebsos]

+1

I already wrapped the components in a View, but got this error. After that any TouchableHighlight in my App throwed this error. Solved it (temporary?) by clearing the app data in settings. The problem occurred in Android, Emulator, Win10, RN 0.42.3 with "Debug JS Remotely" without "Hot Reloading".

[mr-bat]

same here

[mr-bat]

+1

[jp928]

• 1

[adamnator92]

+1 happen when i switch navigator

[zorosun]

+1

[TheIndianRaj]

Got the same error. Rebuilding the app from XCode solved it for me.

[irekrog]

+1

[emrehayirci]

+1

[langjun]

+1

[cjie]

+1

[jurby]

+1

[zywj]

+1

[oldmilk]

+1

[sharingjingang050241]

+1

[alexwan02]

+1

[dhyegocalota]

+1

[blackflamedigital]

Any progress on this?

[pandilladivya]

This problem occurs when I debug remotely .

[guilhermepontes]

anyone?!

[eggybot]

after developing for 3weeks suddenly this issue appear when I use the nativebase Fab component. I hope F8 can fix this issue

[kozillla]

Have the same issue,

[ghost]

+1

[pecopeco]

+1

[jonathanroze]

+1

[BerndWessels]

+1

    render() {
        let {onNavigateToOfferScreen, navigation} = this.props;
        let {dataSource} = this.state;
        return (
            <ListView style={styles.container} dataSource={dataSource} renderRow={offer => (
                <TouchableHighlight onPress={() => onNavigateToOfferScreen(offer)}>
                    <View style={styles.row} elevation={2}>
                        <Text style={styles.businessName}>{offer.name}</Text>
                    </View>
                </TouchableHighlight>
            )}/>
        );
    }

[XueChenChen]

+1

[didierfranc]

Idem

[emmajam]

+1

[gaussz]

+1

[samstr]

+1

[liuzhen88]

+1

[chuyihuang]

+1 .... this error just pop up after i start using fetch...

[yash2code]

same issue additional view not working

[MrToph]

+1

[ricardokdz]

+1

[ghulamMustafaRaza]

count++

[charlesdeb]

+1

[fungilation]

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

[dhyegocalota]

@fungilation 👍

[Jarrio]

+1

This only happens with remote debugging and I fixed this temporarily by doing the following:

1. Open Android Settings
2. Apps
3. Click on your Application
4. Storage
5. Clear Cache

---

Note: This really is a temporary solution. It still repeatedly pops up every now and then.

[quydongnast]

@Jarrio Thanks

[Jarred-Sumner]

@lukemiles thoughts?

[pansitwattana]

+1

[codebeautiful]

+1

[abartolo]

+1

[Rebsos]

@Jarrio 's tmp solution works for now

[JonasLaux]

+1

[behzad888]

+1

[betko]

+1

[learnmove]

rn 48 +1,

[AlmogRnD]

+1

[ollydixon]

rn 48 + 1

[tundak]

Issue occurred only if remote js debug enabled... with normal mode it is working fine.

[Jetsly]

rn 49.3+ 1

[dannyshisler]

+1

[alexHlebnikov]

+1

[bcbane]

+1

[rfw]

+1

[callmejm]

I change TouchableHighlight to TouchableOpacity , it not happen

[trumpetx]

RN.50 +1

[karltaylor]

@Jarrio still throws the error straight away on android

[shadowm2]

+1 0.47

[imfeng]

[email protected] +1

[yoandypv]

+1

[alanyong91]

PLEASE STOP +1 !!!

[luck2011]

uh... plus 1, then

[denny64]

+1

[nikolaystrikhar]

+1

[windhost]

+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.

[psivanov]

+1

[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

[PerspectivesLab]

+1

[sandrojurado]

In LibrariesComponentsTouchableTouchableHighlight.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.

[filipemerker]

+1

[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.

[pacozaa]

+1

[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`

[drpark]

+1

[KoreSamuel]

+1

[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.