Repository navigation
setTimeout and setInterval don't fire on Android RN 0.31 when attached to Chrome Debugger #9436
Description
setTimeout(() => console.log("#############", 1000);
setInterval(() => console.log("#############", 1000);
NetInfo.fetch().done(v => console.log(v));
not fire on android RN 0.31 but fire on RN 0.30
Env: Mac os 11.6
Reacted by Jacob Parker
Activity
[-]setTimeout setInterval not fire on Android[/-][+]setTimeout setInterval not fire on Android RN 0.31[/+]satya164 commentedon Aug 16, 2016
Facing the same issue when I connect to chrome debugger.
rigdern commentedon Aug 16, 2016
Is this related to #9319?
nihgwu commentedon Aug 16, 2016
what about #4470 , seems it's not a regression, but a knowing bug for quite a long time
satya164 commentedon Aug 16, 2016
@nihgwu in this case it doesn't fire at all. I can reproduce this issue when I upgrade from RN 0.30. Haven't gotten the time to make a reproducible sample.
@rigdern might be
c-h- commentedon Aug 17, 2016
Having same issue RN 31 while debugging with Chrome only
satya164 commentedon Aug 18, 2016
Ok, successfully reproduced this with a new project.
Steps to reproduce,
react-native init TimerBug cd TimerBug react-native run-androidindex.android.jsSee YellowBox coming up
It never fires
cc @bestander
[-]setTimeout setInterval not fire on Android RN 0.31[/-][+]setTimeout and setInterval don't fire on Android RN 0.31 when attached to Chrome Debugger[/+]mkonicek commentedon Aug 20, 2016
This might be related to the new bridge on Android and #9319 (
AsyncStorage.getAllKeycallback doesn't get called when debugging).I'll ping @cjhopman and @mhorowitz on fb@work messenger.
lexs commentedon Aug 23, 2016
I found the problem and a fix should make it to the next release. We we're accidentally dropping all native calls made during loading of the JS bundle which causes the thing that was driving the queue to not be called.
satya164 commentedon Aug 23, 2016
@lexs We can probably cherry-pick this to current release?
lexs commentedon Aug 24, 2016
@satya164 Sure, commit is here: b4999fc
Closing this issue now.
21 remaining items
mhdizade commentedon Sep 20, 2017
I set the device time exactly with the debugger time and it works ;)
Fr33maan commentedon Oct 27, 2017
For whom guess how to update device time, use adb from a terminal:
adb shell su root date $(date +%m%d%H%M%Y.%S)It was the solution for me, now events fire correctly
jordanmkoncz commentedon Jan 24, 2018
I had to also fully restart my Android Emulator after running the
adb shellcommand for updating device time in order to get things working again when remote JS debugging is enabled.hstarorg commentedon Feb 1, 2018
Same issue in rn 0.52.1
willbattel commentedon Mar 11, 2018
Still getting this in 0.53.3.
dhirendrarathod2000 commentedon Mar 19, 2018
RN 0.53 Same issue
For me it does not work on either
lodi-g commentedon Mar 19, 2018
RN 0.54 ; getting this issue as well.
srikanthkyatham commentedon Apr 5, 2018
RN 0.53 android - I was able to resolve following the trick here
https://stackoverflow.com/a/39304401/1177995
isaachinman commentedon Apr 22, 2018
Experiencing this issue on v0.54.2. Any fixes?
dgurns commentedon May 3, 2018
Same here, v0.54.0
dogofpavlov commentedon May 7, 2018
Got the same issue as well, just starting into ReactNative and discovering things like makes me cautious moving forward, this seems pretty basic.
Sharcoux commentedon May 12, 2018
Need to sync debugging computer with device. Execute on your computer: