Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debug in Chrome feature can not work in this project #16

Closed
laozhuang727 opened this issue Oct 4, 2015 · 6 comments
Closed

Debug in Chrome feature can not work in this project #16

laozhuang727 opened this issue Oct 4, 2015 · 6 comments

Comments

@laozhuang727
Copy link

Hi,

This is a great "react native" demo for android. With the latest version, when I enable the "debug in chrome" option. The app stop in the Welcome page. And can not render the home page.

It bring a big challenge for dev debugging.

Would you please help to take a look and provide a solution?

Thanks & Regards,
Ryan

@race604
Copy link
Owner

race604 commented Oct 4, 2015

Debugging work perfect for me. Please check if you add some break points in the Chrome?

@laozhuang727
Copy link
Author

Hi race,

Which react-native version are you using now? Is it 0.11.4?

It seems in RCTZhiHuDaily, the setTimeOut function did not work. So the this.state.splashed==false. And it will keep render the SplashScreen, and can not update the Navigator component.

Thanks & Regards,
Ryan

@laozhuang727
Copy link
Author

It is so Strange that, the TimerMixin setTimeout function is working fine in run model. But it is not trigger in debug model.

@laozhuang727
Copy link
Author

I finally found the issue myself. The root cause is I was using genymotion as the mobile visual device.
The timestamp setting in the visual device is different with current time (which is about 1 year different).

After change the timestamp in the visual device. The debug is working fine now.

Thanks a lot for your support!!

Regards,
Ryan

@race604
Copy link
Owner

race604 commented Oct 5, 2015

Thank you Ryan. This is a great issue, I'll fix this bug when system time is not correct.

@race604
Copy link
Owner

race604 commented Oct 10, 2015

All right, this seems is JavaScript Runtime problem, I'll close this issue. Please make sure your device/emulator time is sync with your Computer when debugging.

@race604 race604 closed this as completed Oct 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants