[ios] main.jsbundle is not found

[gorangajic]

When I archive the project and try to run on the real device app just closes with this error message

Nov 28 16:09:09 [3113] : The specified JS bundle file wasn't found within the app's binary. Is "main.jsbundle" the correct file name?
Nov 28 16:09:09 (CoreFoundation)[3113] : *** Terminating app due to uncaught exception 'RCTFatalException: The specified JS bundle file wasn't found within the app's binary. Is "main.jsbundle" the correct file name?', reason: 'The specified JS bundle file wasn't found within the app's binary. Is "main...'

I have used react-native link to link code-push and I have checked manually if everything is linked and I didn't find anything wrong.
Also, I have run

code-push release-react MyApp-ios ios
code-push promote MyApp-ios Staging Production

Any ideas?

• react-native-code-push version: 1.16.0-beta
• react-native version: "0.35.0"

[richardhuaaa]

Hi @gorangajic, does this error happen the first time the app is run, before the CodePush update is applied, or after an update is applied?

[joshyg]

I am seeing the same thing after upgrading react native from 0.25.1 to 0.38.0:

*** Terminating app due to uncaught exception 'RCTFatalException: The specified JS bundle file wasn't found within the app's binary. Is "main.jsbundle" the correct file name?', reason: 'The specified JS bundle file wasn't found within the app's binary. Is "main...'

[gorangajic]

I have figured out my problem, dependencies were installed using npm@2 and after installing npm@3 and reinstalling dependencies again everything was fine.

@joshyg I will close this issue, if you want to stay open I will reopen

[richardhuaaa]

That is very strange, so that's good to know. Thanks so much for the update!

[adbl]

Seeing this same problem on first run with Code Push support, release build on development device, there is no update pushed yet.

2017-01-12 14:16:27.942 [fatal][tid:main] The specified JS bundle file wasn't found within the app's binary. Is "main.jsbundle" the correct file name?
2017-01-12 14:16:27.943646 ShimClient[2036:685353] The specified JS bundle file wasn't found within the app's binary. Is "main.jsbundle" the correct file name?
2017-01-12 14:16:27.944034 ShimClient[2036:685353] *** Terminating app due to uncaught exception 'RCTFatalException: The specified JS bundle file wasn't found within the app's binary. Is "main.jsbundle" the correct file name?', reason: 'The specified JS bundle file wasn't found within the app's binary. Is "main...'

[adbl]

Ignore that, the packager failed to build, but didn't stop xcode build 😨

[iSimar]

The specified JS bundle file wasn't found within the app's binary. Is "main.jsbundle" the correct file name?
libc++abi.dylib: terminating with uncaught exception of type NSException

Getting this error after trying to build for external device. Scheme is set to release.

[sergey-akhalkov]

@iSimar - hi!
Please verify if you able to build main.jsbundle file using following command:
react-native bundle --platform ios --dev false --entry-file index.ios.js --bundle-output ios/main.jsbundle.
If so, could you please provide me with content of AppDelegate.m file?

[mrshll]

@sergey-akhalkov I am running into the same problem, perhaps I can shed some light:

#ifdef DEBUG
    jsCodeLocation = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index.ios" fallbackResource:nil];
#else
    jsCodeLocation = [CodePush bundleURL];
#endif

  RCTRootView *rootView = [[RCTRootView alloc] initWithBundleURL:jsCodeLocation
                                                      moduleName:@"AppName"
                                               initialProperties:nil
                                                   launchOptions:launchOptions];

The CodePushDeploymentKey is definitely in my Info.plist. I have CodePush functioning properly in another project, but I'm still having trouble diffing to figure out what is going wrong.

I have released to Staging twice, and promoted to Production once:

The moduleName is the exact same as my AppRegistry's registered component.

[sergey-akhalkov]

@mmoutenot, do I understand that correct that you have [ios] main.jsbundle is not found error?
If so, could you please provide me with the command(s) you are using for releasing CodePush updates for iOS?
Also it would be very helpful if you could provide me with react-native-code-push version, react-native version, repro steps and/or stack trace.

[mrshll]

@sergey-akhalkov that is correct. When I try to run a Release build on my physical device (and therefore retrieve the bundle from codepush) that is the error I get.

The command I use to release is code-push release-react HerpAtlasReporter ios
My version of react-native is 0.40.0, of react-native-code-push is 1.17.0-beta.

Steps:

1. I created a react native app.
2. I added and linked react native code push
3. I created a new app for code push, adding the distribution keys to the info.plist, and the code to check for updates in my react app
4. I change my scheme to Release and run. It fails to run on a physical device with the above error message.

I am sure it's something stupid I've misplaced or mistaken, as I have another app working with codepush...

Thanks for your help.

[mrshll]

It may have been a problem with my node version? By changing the Run script build phase:

-                       shellScript = "export NODE_BINARY=node\n../node_modules/react-native/packager/react-native-xcode.sh";
+                       shellScript = "nvm use\nexport NODE_BINARY=$(which node)\n../node_modules/react-native/packager/react-native-xcode.sh";

The app now properly runs in Release. I think the problem was that the build was succeeding, but built with an incorrect node version it was unsupported? Huh, cool!

[sergey-akhalkov]

@mmoutenot, hmm, seems like you've experienced environment specific problem, you could try to run commands following below and use generated output to determine what version of node causes the issue:

$ nvm ls
...
$ node
> [ process.argv, process.release ]
...

Please let me know if the issue is resolved or if you need any help.