-
Notifications
You must be signed in to change notification settings - Fork 905
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
react-native link @react-native-community/async-storage fails #273
Comments
Can you reinstall |
Same thing after a complete clean. |
I couldn't reproduce on a clean project. Can you set up a repo with reproduction so we can investigate? |
I'll have to admit, "error Something went wrong while linking." is not the greatest error message. It seems like the stack trace is eaten. Perhaps we could start by displaying the full stack trace of the fatal error message and see what object "matched" is called on. Let me see if I can re-create it outside an my private project. |
FYI @krizzu |
Getting the same not sure what it is, I also got it for
|
I'll try to reproduce it and fix this. It's definitely a bug somewhere in the linking logic that might be happening due to specific structure of your project. |
This appears to be longer reproducible after an upgrade to 0.59.3.
I'm not sure if this error stops the link execution and hides the previous error. With the CLI, are all the errors reported or the does an error fail fast? Thanks. |
I'll check this out tonight thanks for the update @patrice4github |
Can't reproduce on master with any of the packages and fresh |
Too bad we can't reproduce it. About this:
I think we should focus on displaying the stack trace of such error. The code crashes, knowing where would give us the cause of the error right away, pretty much. Just a suggestion. |
Right, give me a second, I'll publish a patch with a fix for that! |
@patrice4github please try to re-install |
Linking AppCenter doesn't work too. Will check |
We ran into this when upgrading react-native versions with a project name containing a dash (it worked fine before the upgrade). |
run -------- react-native link react-native-webview error Something went wrong while linking. Error: Expected "/ Begin ", "/ End ", """, or [A-Za-z0-9_.] but "<" found. |
@codeprolin can you open your project with Xcode and then, run |
@zbluephoenix thanks! @grabbou the error comes from |
@thymikee thank you for your reply。 I found a solution.
$ react-native link react-native-gesture-handler --verbose |
Thanks for posting this! I can see the code is designed to expect this line which is very weird design choice. It could be named better, like "DO NOT REMOVE. THIS IS FOR CLI POD INTEGRATION TO WORK" or so. Maybe we can squeeze the change to 0.60. |
We should definitely fix it by adding a better error message. I am going to work on it now. |
@zbluephoenix what is the name of your |
YYHQApp.xcodeproj |
Thanks! So the issue is you have an array of targets and no text marker.
I’ve just shipped a better error message to explicitly say what needs to be
done in order to make link work.
This is going to be much better when we ship autolinking soon.
Meanwhile, I believe we can close this issue since it’s expeced.
…On Wed, 17 Apr 2019 at 01:38, JabinZheng ***@***.***> wrote:
platform:ios,’9.0’
inhibit_all_warnings!
targetsArray = ['YYHQApp','YYHQApp_Pro']
targetsArray.each do |t|
target t do
pod 'RNGestureHandler', :path => '../node_modules/react-native-gesture-handler'
end
end
YYHQApp.xcodeproj
@grabbou <https://github.com/grabbou>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#273 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACWcxv1Cii0_edrZ4JXCDkiz6O6Kc9Cfks5vhl74gaJpZM4cOdxZ>
.
|
I'm getting this error while trying to link custom fonts directory with
Note: we are using lerna and RN project is under the react-native-cli: 2.0.1 |
@berdyshev this is not a valid way to use
|
@thymikee ok, thank you. should I run any command after that? Or just restart the react-native's packager? |
Yes, you need to run |
@thymikee I have pretty same issue as @berdyshev even if
|
@berdyshev I have found a workaround. |
The same here:
|
I am having the same problem while installing fonts. I tried react-native-asset as suggested by @devproivansurzhenko and the fonts were still not installed. @thymikee I followed your steps to install fonts and added but still see same error upon react-native link |
It would be great if you provided a source code somewhere (can be via private Github invitation) so we could look into that and fix it. It's hard to debug locally w/o reproduction. |
@awesomeo99 did you receive any error at |
Interesting... created an RN app from scratch. |
Workaround: doing
Environment
Package.json
|
Folks, using react-native link # good
react-native link react-native-config # good
react-native link @react-native-community/async-storage # good
react-native link ./some/path # bad, unsupported, it will try to use the path as npm package, that's why you get dependency error – it's not a dependency |
i'm getting this error while linking the async storage
|
This has been fixed in #321 and now, the error message is:
I am going to lock it. Going to be released as a part of 0.60. |
FYI this was fixed in the v2 of the CLI and wasn't yet ported to |
Went ahead and ported it to 1.x: https://github.com/react-native-community/cli/releases/tag/v1.9.5. Hope it's gonna be easier to track the problem now! |
Environment
Description
The link in this new lib fails. The commands states to to log a bug:
Reproducible Demo
react-native link @react-native-community/async-storage
The text was updated successfully, but these errors were encountered: