I just starting trying out the hot loading on my log screen of my app.
I am getting the following being emmitted to my debug console and the app is consistently reloading itself.
I actually have to kill simulator to get out of this state.
[RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 0
2016-03-22 20:24:48.376 [fatal][tid:com.facebook.React.JavaScript] Unable to execute JS call: __fbBatchedBridge is undefined
2016-03-22 20:24:49.497 [info][tid:NSOperationQueue 0x7f80e9754120 :: NSOperation 0x7f80eb9cb880 (QOS: LEGACY)][RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 0
2016-03-22 20:24:50.515 [info][tid:NSOperationQueue 0x7f80e9754120 :: NSOperation 0x7f80e97c7ec0 (QOS: LEGACY)][RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 0
2016-03-22 20:24:50.741 [info][tid:NSOperationQueue 0x7f80e9754120 :: NSOperation 0x7f80e946abd0 (QOS: LEGACY)][RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 0
2016-03-22 20:24:52.509 [info][tid:NSOperationQueue 0x7f80e9754120 :: NSOperation 0x7f80ebc83b30 (QOS: LEGACY)][RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 0
2016-03-22 20:24:53.248 [info][tid:NSOperationQueue 0x7f80e9754120 :: NSOperation 0x7f80ebabef10 (QOS: LEGACY)][RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 0
2016-03-22 20:24:55.028 [info][tid:com.facebook.React.JavaScript][RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 4
2016-03-22 20:24:55.620 [info][tid:NSOperationQueue 0x7f80e9754120 :: NSOperation 0x7f80ebd3e910 (QOS: LEGACY)][RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 0
2016-03-22 20:24:56.024 [info][tid:NSOperationQueue 0x7f80e9754120 :: NSOperation 0x7f80e97f74b0 (QOS: LEGACY)][RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 0
2016-03-22 20:24:56.670 [info][tid:com.facebook.React.JavaScript][RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 4
2016-03-22 20:24:56.788 [info][tid:NSOperationQueue 0x7f80e9754120 :: NSOperation 0x7f80ebcd2c00 (QOS: LEGACY)][RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 0
Basically unusable here. If you need more information ping me here I would love to use this feature for quicker design etc.
Similar error code has been references in this issue. #3747
Live reload seems to work fine.
Everything seems to work fine until hot reload is turned on, and then it just throws that error a few times a second and app keeps trying to reload until it eventually crashes or simulator is quit.
Live reload still works as it used to. Seems like something in our app is not happy to be hot reloaded, but unclear where to look since this error is not very informative...
Some tips about what that error means or where to look would be appreciated.
As per the line that says Unable to execute JS call: __fbBatchedBridge is undefined looks like there's an error loading the JS bundle.
Could you try getting it using curl maybe? curl "localhost:8081/index.ios.js?platform=ios"?
I'm getting this too, trying to upgrade from 0.19 to 0.22. Pinging curl "localhost:8081/index.ios.js?platform=ios"?returns code.
The simulator is constantly reloading, with the specific error repeating:
2016-04-01 13:48:08.117 [info][tid:NSOperationQueue 0x7f8c13d0eb40 :: NSOperation 0x7f8c13ebbb20 (QOS: LEGACY)][RCTPerformanceLogger.m:29] Unbalanced calls start/end for tag 0
Digging into my node_modules/react-native/package.json I see that I have
"bin": {
"react-native": "local-cli/wrong-react-native.js"
},
Trying to reinstall globally doesn't work as suggested in https://github.com/facebook/react-native/issues/4515#issuecomment-173302985
After walking away from this for a few days, and again attempting to upgrade 0.19 to 0.22 - I was getting this behavior again (constantly reloading, can't click on Disable Hot Loading within developer menu because of constant reloading). Resolved it by resetting the simulator's content and settings (Simulator > Reset Content and Settings) and re-running.
Seems like the local-cli/wrong-react-native.js I mention in the comment above was a red herring -- my package.json still has that wrong-react-native.js set
hmm interesting i will check it out! @aaronschachter
we managed to fix this by cleaning up our index.ios to closer match a brand new react project. We first started at around 0.11 so a lot of stuff had diverged since then. Not sure exactly what the original cause was, but many things were going wrong. We finally got hot reload working by a combination of wrapping navigator in a view, extending component instead of the old create class, switching to es6 syntax, removing mixins, setting a fixed dimensions on the parent container, specifying platform type in the appdelegate JS, etc.
Now there is a red border around the thing when hot reload is on (is that normal?), but besides that is works quite smoothly.
So, I fixed this issue by replacing:
jsCodeLocation = [NSURL URLWithString:@"http://0.0.0.0:8081/index.ios.bundle"];
with
jsCodeLocation = [NSURL URLWithString:@"http://0.0.0.0:8081/index.ios.bundle?platform=ios&dev=true"];
in my app delegate
馃檲
Make sure you don't have any tasks running (i.e. Dropbox) inside your project folder that can cause changes to the contents of your project, this will trigger the continuous reload.
It looks like this is workarounded so I am going to close this issue. Thanks folks for helping out!
Most helpful comment
Make sure you don't have any tasks running (i.e. Dropbox) inside your project folder that can cause changes to the contents of your project, this will trigger the continuous reload.