-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
[0.46.3] fails to run on device #14912
Comments
That seems strange. Is this something you can reliably reproduce? For example, does it occur on a plain new project created with 0.46.1? |
yes, create a plain new project and it fails for me. |
@hramos any updates here? RN 0.46.3 has the same issue. 0.46.x is basically unusable because of this issue. As I said, it happens on a new project when trying to run it on the device using "Release" config. It should be very simple to reproduce. |
I don't have any updates, I haven't seen any PR that addresses this specifically. If one is submitted and merged in, I can look into another point release. |
Solved it. It seems that packager is trying to figure out node version installed on my system. The problem was that I am using nvm and default nvm node version was |
@ivpusic Hi, I too have this problem. When I deploy my app to a device when compiled for
I'm not using nvm - is there an alternative for brew? Node version is v8.2.0 Debug mode works fine (loading the bundle off my laptop) |
resolving node binary/version is done here https://github.com/facebook/react-native/blob/master/scripts/react-native-xcode.sh#L54. Try to put some debug logs to see what is resolved. |
having this issue as well. |
if you ever installed https://github.com/facebook/react-native/blob/master/scripts/react-native-xcode.sh#L58
|
Is this a bug report?
yes
Environment
Target Platform: iOS
Steps to Reproduce
Build iOS app for release, and try to run it on the actual iOS device.
The app will crash with error:
On the simulator, the app runs fine.
After downgrading to 0.45.1 everything worked on the device as well again.
The text was updated successfully, but these errors were encountered: