-
Notifications
You must be signed in to change notification settings - Fork 553
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
installation #24
Comments
Hi May be some setting is wrong/non-standard in your android project. You can manual add the config.
for detail, you can init a new project and diff with my example project. |
Thanks so much for your assistance as a deeper dive indeed fixed the issues. |
react-native link failed for me in RN 0.54, these instructions helped a lot! |
With reference to issue #2, |
Is there any manual Installation for IOS? |
|
Note that |
Hi.
While I have no problems with IOS with the exact setup I've tried to install on a few windows 10 comptuters with RN 0.41 and get the following error
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\React\nsp\NSPV6\NativeStarterPro-v6.0.0>npm install react-native-pdf --save
react-native-pdf@1.2.4 node_modules\react-native-pdf
├── crypto-js@3.1.9-1
└── react-native-fetch-blob@0.10.6 (glob@7.1.2)
C:\React\nsp\NSPV6\NativeStarterPro-v6.0.0>react-native link react-native-pdf
rnpm-install info Linking react-native-pdf android dependency
rnpm-install ERR! It seems something went wrong while linking. Error: ENOENT: no such file or directory, open 'C:\React\nsp\NSPV6\NativeStarterPro-v6.0.0\android\app\src\main\java\android\support\v7\appcompat\MainApplication.java'
Please file an issue here: https://github.com/facebook/react-native/issues
ENOENT: no such file or directory, open 'C:\React\nsp\NSPV6\NativeStarterPro-v6.0.0\android\app\src\main\java\android\support\v7\appcompat\MainApplication.java'
I have no problem installing and running your eample on the same win 10 computers, a bit lost.
John
The text was updated successfully, but these errors were encountered: