React-native: Attempted to transition from state `RESPONDER_INACTIVE_PRESS_IN` to `RESPONDER_ACTIVE_LONG_PRESS_IN`, which is not supported.
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
samhunta
All 162 comments
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-nativeor 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!
facebook-github-bot
on 8 Feb 2016
I get the same error when testing on an iPhone6 (9.1)
casperin
on 9 Feb 2016
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?
grabbou
on 24 Apr 2016
+1
I also get this problem,and It's happened frequently switch navigator
askday
on 28 Apr 2016
Going to close it as @askday also put better repro in the #1693. Please reopen if OP mentioned something different.
grabbou
on 28 Apr 2016
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
radek1991
on 23 Aug 2016
+1
stief510
on 31 Aug 2016
+1
charlesLin
on 7 Sep 2016
+1
pawellewandowski
on 20 Sep 2016
+1
minhchu
on 22 Sep 2016
:+1:
gillestasse
on 22 Sep 2016
👍
Jarred-Sumner
on 24 Sep 2016
+1
StevenKing9
on 3 Oct 2016
+1
bucketclan
on 25 Oct 2016
+1
myseven
on 26 Oct 2016
+1
SerzN1
on 9 Nov 2016
+1
johnjichaowei
on 13 Nov 2016
+1
berkaybeyaz1
on 16 Nov 2016
+1
dadbob
on 16 Nov 2016
+1
nadeermalangadan
on 19 Nov 2016
+1
ouabing
on 28 Nov 2016
I am also having this error, but only on Android. IOS is working as expected.
nikolal
on 29 Nov 2016
+1
chandlervdw
on 30 Nov 2016
+1
helloncanella
on 1 Dec 2016
+1
Yangzhedi
on 6 Dec 2016
+1
wasa4587
on 7 Dec 2016
+1
pyshchyk-o
on 7 Dec 2016
+1
haloJim
on 8 Dec 2016
+1
mp31415
on 8 Dec 2016
+1 same error only on Android but iOS works fine.
binzailani3136
on 8 Dec 2016
+1 same as @binzailani3136
getnashty
on 12 Dec 2016
+1
timsawtell
on 12 Dec 2016
恭喜此bug当选 RN0.39版 最臭名昭著的issue之一
Yangzhedi
on 13 Dec 2016
+1
futurechallenger
on 14 Dec 2016
+1
tqqttq
on 14 Dec 2016
+1
banzheshenghuo
on 14 Dec 2016
+1
XinQiXiao
on 14 Dec 2016
+1
lucaschain
on 14 Dec 2016
+1
zlllya
on 15 Dec 2016
+1
bdart
on 15 Dec 2016
+1
BabuinGH
on 15 Dec 2016
Guys, your +1s aren't helpful, and this is in #1693
braco
on 20 Dec 2016
+1
BeckZero
on 23 Dec 2016
+1
a-eid
on 6 Jan 2017
+1
KamWis
on 7 Jan 2017
+1
felipembbraga
on 11 Jan 2017
+1
kylin93
on 12 Jan 2017
+1
UlfR
on 17 Jan 2017
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
magrinj
on 19 Jan 2017
+1
JumalDB
on 24 Jan 2017
+1
leoabacade
on 25 Jan 2017
@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?
fungilation
on 25 Jan 2017
@fungilation Maybe I did a mistake by opening a new ticket, because this one is open and talk about the same problem: #1693
magrinj
on 26 Jan 2017
Fixed after add View
<TouchableNativeFeedback>
<View> // <= here
<Text style={css.item}>{rowData.title + rowData.id}</Text>
</View>
</TouchableNativeFeedback>
Yadro
on 29 Jan 2017
@Yadro, you mean inserting additional View fixes this from the app side, or RN can fix it internally by doing so?
fungilation
on 30 Jan 2017
hm, my English is bad, but inserting additional View resolve this problem
Yadro
on 30 Jan 2017
Ok. I'll report back if I still hit this issue with additional Views
fungilation
on 30 Jan 2017
+1
edencakir
on 10 Feb 2017
I only get this when I'm in remote debugging. This doesn't happen normally. RN .41.2. Windows 10. Android
ckwong90
on 16 Feb 2017
+1
jose920405
on 16 Feb 2017
@ckwong90, some here, only apears when remote debugging
RN .41.2. macOS Sierra 10.12.3
sergchil
on 22 Feb 2017
- 1 same problem
baotoan1905
on 14 Mar 2017
Same here, Android 6.0, latest RN, remote debugging
volodymyrrudyi
on 18 Mar 2017
+1
martinjobb
on 23 Mar 2017
+1
whyming
on 24 Mar 2017
+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.
xingjianpan
on 25 Mar 2017
+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".
Rebsos
on 6 Apr 2017
same here
mr-bat
on 20 Apr 2017
+1
mr-bat
on 20 Apr 2017
- 1
jp928
on 29 Apr 2017
+1 happen when i switch navigator
adamnator92
on 2 May 2017
+1
zorosun
on 4 May 2017
Got the same error. Rebuilding the app from XCode solved it for me.
TheIndianRaj
on 6 May 2017
+1
irekrog
on 6 May 2017
+1
emrehayirci
on 9 May 2017
+1
langjun
on 12 May 2017
+1
cjie
on 12 May 2017
+1
jurby
on 16 May 2017
+1
zywj
on 19 May 2017
+1
oldmilk
on 19 May 2017
+1
sharingjingang050241
on 22 May 2017
+1
alexwan02
on 22 May 2017
+1
dhyegocalota
on 31 May 2017
Any progress on this?
blackflamedigital
on 31 May 2017
This problem occurs when I debug remotely .
pandilladivya
on 1 Jun 2017
anyone?!
guilhermepontes
on 1 Jun 2017
after developing for 3weeks suddenly this issue appear when I use the nativebase Fab component. I hope F8 can fix this issue
eggybot
on 1 Jun 2017
Have the same issue,
kozillla
on 11 Jun 2017
+1
ghost
on 15 Jun 2017
+1
pecopeco
on 26 Jun 2017
+1
jonathanroze
on 28 Jun 2017
+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>
)}/>
);
}
BerndWessels
on 5 Jul 2017
+1
XueChenChen
on 5 Jul 2017
Idem
didierfranc
on 6 Jul 2017
+1
emmajam
on 10 Jul 2017
+1
gaussz
on 11 Jul 2017
+1
samstr
on 15 Jul 2017
+1
liuzhen88
on 18 Jul 2017
+1 .... this error just pop up after i start using fetch...
chuyihuang
on 19 Jul 2017
same issue additional view not working
yash2code
on 22 Jul 2017
+1
MrToph
on 22 Jul 2017
+1
ricardokdz
on 28 Jul 2017
count++
ghulamMustafaRaza
on 28 Jul 2017
+1
charlesdeb
on 28 Jul 2017
STOP with the +1 spam. Just give the original post or whichever comment a thumbs up 👍🏼 if you see the same.
fungilation
on 28 Jul 2017
@fungilation 👍
dhyegocalota
on 28 Jul 2017
+1
This only happens with remote debugging and I fixed this temporarily by doing the following:
- Open Android Settings
- Apps
- Click on your Application
- Storage
- Clear Cache
Note: This really is a temporary solution. It still repeatedly pops up every now and then.
Jarrio
on 8 Aug 2017
@Jarrio Thanks
quydongnast
on 9 Aug 2017
@lukemiles thoughts?
Jarred-Sumner
on 9 Aug 2017
+1
pansitwattana
on 19 Aug 2017
+1
codebeautiful
on 24 Aug 2017
+1
abartolo
on 26 Aug 2017
@Jarrio 's tmp solution works for now
Rebsos
on 26 Aug 2017
+1
JonasLaux
on 28 Aug 2017
+1
behzad888
on 7 Sep 2017
+1
betko
on 11 Sep 2017
rn 48 +1,
learnmove
on 16 Sep 2017
+1
AlmogRnD
on 28 Sep 2017
rn 48 + 1
ollydixon
on 4 Oct 2017
Issue occurred only if remote js debug enabled... with normal mode it is working fine.
tundak
on 4 Oct 2017
rn 49.3+ 1
Jetsly
on 12 Oct 2017
+1
dannyshisler
on 14 Oct 2017
+1
alexHlebnikov
on 17 Oct 2017
+1
bcbane
on 20 Oct 2017
+1
rfw
on 25 Oct 2017
I change TouchableHighlight to TouchableOpacity , it not happen
callmejm
on 27 Oct 2017
RN.50 +1
trumpetx
on 10 Nov 2017
@Jarrio still throws the error straight away on android
karltaylor
on 6 Dec 2017
+1 0.47
shadowm2
on 7 Dec 2017
imfeng
on 9 Dec 2017
+1
yoandypv
on 17 Dec 2017
PLEASE STOP +1 !!!
alanyong91
on 18 Dec 2017
uh... plus 1, then
luck2011
on 20 Dec 2017
+1
denny64
on 21 Dec 2017
+1
nikolaystrikhar
on 25 Dec 2017
+1 for 0.48.3
windhost
on 25 Dec 2017
+1 on 0.51.0
JaEdmuva
on 28 Dec 2017
+1 is nice, love it. Happens of 0.50
Fortidude
on 29 Dec 2017
+1
TimorYang
on 3 Jan 2018
+1
giovanniRodighiero
on 9 Jan 2018
+1
with react-native 0.51.0
iotdog
on 14 Jan 2018
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.
basbase
on 17 Jan 2018
+1
psivanov
on 30 Jan 2018
+1
roshanpal
on 4 Feb 2018
+1
MedinaGitHub
on 7 Feb 2018
+1
sizovilya
on 7 Feb 2018
+1
anwarhamr
on 8 Feb 2018
+1
vvavepacket
on 11 Feb 2018
Solution to me was to
- Ensure phone and pc got same timezone
- Manually update time on pc: Date and Time -> Internet Time tab -> Change Settings -> Update Time
- Toggle-on auto time update in android settings, then toggle it off
- Restart the app
xemasiv
on 14 Feb 2018
+1
PerspectivesLab
on 21 Feb 2018
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.
sandrojurado
on 22 Feb 2018
+1
filipemerker
on 26 Feb 2018
+1
brzonsea
on 1 Mar 2018
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.
b45ch1
on 4 Mar 2018
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.
Benzer1406
on 8 Mar 2018
+1
pacozaa
on 10 Mar 2018
+1
abaddonGIT
on 12 Mar 2018
automatic time setting on android device and automatic time setting on computer solved the problem
guitar9
on 18 Mar 2018
on Ubuntu I synchronized system time with the current ADB time by doing :
sudo date +%T -s `adb shell date +%T`
remigarcia
on 21 Mar 2018
+1
drpark
on 22 Mar 2018
+1
KoreSamuel
on 30 Mar 2018
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.
hramos
on 4 Apr 2018
Related issues
lazywei
·
3Comments
vikeri
·
3Comments
upbit
·
3Comments
jobsamuel
·
3Comments
oney
·
3Comments
Most helpful comment
Fixed after add View