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

Running project with release config fails #14751

Closed
veris-amoghbanta opened this issue Jun 27, 2017 · 7 comments
Closed

Running project with release config fails #14751

veris-amoghbanta opened this issue Jun 27, 2017 · 7 comments
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.

Comments

@veris-amoghbanta
Copy link

Description

Running react-native project with release config via Xcode fails and gets stuck to the screen below. There is no error or stack trace to find the reason behind it. Everything works smoothly in debug mode.
screen shot 2017-06-27 at 8 03 04 pm

Reproduction Steps

  • change the run config to release via product/scheme in Xcode
  • run on any iOS simulator
  • React Native version: 0.44.2, react: 16.0.0-alpha.6
  • Platform: iOS, Android
  • Development Operating System: macOS Sierrra 10.12.5
  • Build tools:Xcode 8.3.3
@veris-amoghbanta
Copy link
Author

This is an issue with bundling.
react-native bundle --platform ios --dev false --entry-file index.ios.js --bundle-output iOS/main.jsbundle gives the following error:

SyntaxError: Unterminated string constant

Bundling with --dev true works as expected.

@lolobosse
Copy link

@veris-amoghbanta Did you solve it? Running into the same issue...

@veris-amoghbanta
Copy link
Author

Wasn't able to pin point the exact cause, but it was some native dependency that caused the bundler to fail silently. So I switched to a new project and installed and linked the exact compatible dependency versions by hand and it seemed to have worked.
Most probably, it was either react-native-elements or react-native-router-flux that was causing the issue in my case.

@pull-bot
Copy link

@facebook-github-bot no-template

1 similar comment
@pull-bot
Copy link

@facebook-github-bot no-template

@facebook-github-bot
Copy link
Contributor

Hey, thanks for reporting this issue! It looks like your description is missing some necessary information, or the list of reproduction steps is not complete. Can you please add all the details specified in the Issue Template? This is necessary for people to be able to understand and reproduce the issue being reported. I am going to close this, but feel free to open a new issue with the additional information provided. Thanks! See "What to Expect from Maintainers" to learn more.

@facebook-github-bot facebook-github-bot added the Ran Commands One of our bots successfully processed a command. label Oct 10, 2017
@facebook-github-bot
Copy link
Contributor

Hey, thanks for reporting this issue! It looks like your description is missing some necessary information, or the list of reproduction steps is not complete. Can you please add all the details specified in the Issue Template? This is necessary for people to be able to understand and reproduce the issue being reported. I am going to close this, but feel free to open a new issue with the additional information provided. Thanks! See "What to Expect from Maintainers" to learn more.

@facebook-github-bot facebook-github-bot added Needs more information Ran Commands One of our bots successfully processed a command. labels Oct 10, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Oct 10, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Oct 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

5 participants