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

Jump to bottom

[0.26.1][iOS] Native UI component hangs application with chrome debugger active #7707

Closed
samfoot opened this issue May 23, 2016 · 7 comments
Closed

[0.26.1][iOS] Native UI component hangs application with chrome debugger active #7707

samfoot opened this issue May 23, 2016 · 7 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@samfoot
Copy link

samfoot commented May 23, 2016 •
edited

I am having an issue when I add an iOS native UI component to a new React Native project the application hangs if you enable the chrome debugger whilst the UI component is included in the project.

I have created a very simple example application here:

https://github.com/spreech/rnnativecompissue

If you run the above it will hang once you enable the debugger. If you comment out RCT_EXPORT_MODULE() at MapViewManager.m:20 and rebuild the app will work correctly even with the debugger attached.

I have been following: https://facebook.github.io/react-native/docs/native-components-ios.html#content

I am using:

OSX
iOS
RN: 0.26.1
@samfoot samfoot changed the title [0.26.1] Native UI component hangs application with chrome debugger active [0.26.1][iOS] Native UI component hangs application with chrome debugger active May 23, 2016
@mikesurowiec
Copy link

I'm experiencing a similar issue on RN 0.26.1. When I enable "debug JS remotely" the simulator will freeze completely

@Elyx0
Copy link

Elyx0 commented May 24, 2016

Confirmed too when using React via Cocoapods. RN 26.2

@mitchellhuang
Copy link

I can confirm this bug exists as well. Frustrating to try and use the debugger to see console.log statements and the whole thing just crashes. RN 0.26.0. I don't think I ran into this issue on 0.25.

@mikesurowiec
Copy link

Just so you all know, I don't experience this issue on 0.27.0-rc

@nikolugano
Copy link

I can confirm this as well. It happens both in simulator and on device (when use development server) and since I moved to 0.26.2. Using react and fbsdk via Cocoapods

@alloy
Copy link
Contributor

alloy commented May 26, 2016

I also had this issue and can confirm that after upgrading to 0.27.0-rc1 the issue is gone.

@alloy alloy mentioned this issue May 26, 2016
Merged
@tarun29061990
Copy link

Still facing this issue while doing transition between screens. Debugging on MotoE and chrome debugger is active. My react-native version is 0.27.2

@facebook facebook locked as resolved and limited conversation to collaborators May 30, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@alloy @brentvatne @Elyx0 @samfoot @mikesurowiec @mitchellhuang @tarun29061990 @nikolugano @react-native-bot