-
Notifications
You must be signed in to change notification settings - Fork 907
restore react-native link functionality #349
Conversation
react-native link doesn't support the new xml format yet, so for now we save it in the old format
Is there any workaround for this? I haven't been able to get even fbsdk v 0.5.0 to work with my new project. |
1DD70E29001F47FB00000002 /* BUCK */ = {isa = PBXFileReference; explicitFileType = text.script.python; path = BUCK; sourceTree = SOURCE_ROOT; }; | ||
1DD70E29001F47FB00000003 /* BUCK */ = {isa = PBXFileReference; explicitFileType = text.script.python; path = BUCK; sourceTree = SOURCE_ROOT; }; | ||
1DD70E2900B6388300000000 /* libRNSDKShareKit.a */ = {isa = PBXFileReference; explicitFileType = archive.ar; name = libRNSDKShareKit.a; path = lib.a; sourceTree = BUILT_PRODUCTS_DIR; }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
path = lib.a
on my machine means XCode will compile multiple different libraries into lib.a
causing all sorts of troubles.
I have to manually set Product Name on each of the targets to stop that from happening.
Otherwise this is a change I'd really love to see merged into master.
As a follow up to my review comment attaching the modifications I have on top of this PR. This addition makes
|
@paulftw I don't know, I just opened the project in Xcode, en saved it again. I didn't change anything. You'll probably have the same issue with xml version? |
Any news about this? Will this be merged back to |
If I run react-native link react-native-fbsdk should I still do the manual setup of android and ios? |
Could it be fixed somehow? It's been already a month since this PR... |
waiting for this as well :| |
Please update this. It is also blocking me. |
Same here. |
Hello? Is anyone here? Do you realise this lib it's a requirement of your company in order to make money: Facebook's campaigns. And there's no alternative. The PR is done. And yet you still don't even answer :/ |
What action is required for this to be merged? |
|
This package is causing all sorts of problems and no one appears to be watching this project. |
@aforty https://code.facebook.com/pages/876921332402685/open-source-code-of-conduct
|
With this branch I'm getting the following. Anyone have any ideas?
|
It's true that we should stay friendly and patient, but it is very frustrating to have this kind of issues open for weeks. You ask for feedback, you get feedback (and a pull request) but this library is still not usable for many people out there, just because we can not get it to work. Right now I'm figuring around how to get this library working without For example what about this note:
I guess this is my problem, but how do I solve this problem if libRCTFBSDK is not showing up there (because linking is not possible). What should I add there? |
As a workaround — which has been mentioned in an other issue too I believe — you can navigate to the library in the |
To get this to work right now I had to do |
@baba43 hope this post will give you a sense of how to do it manually |
@aforty I went into Xcode > Build Phases > Link Binary With Libraries and removed the libRNSDK*.a files listed there. |
Opened on 1st July... ridiculous |
@sospedra Why don't you simply install the one from I solved it this way: Remove the previous one:
Install the fork which is working (this pull request):
Then just remember to follow the setup steps again (remember to link frameworks and to set up the framework search path correctly). By doing this I'm able to run it without any need to tweak the module or xcode project files. Edit: fix to checkout the proper fix branch |
Sorry about the delay in responses everyone Why are you using ios.xcodeproj? You should only be needing RCTFBSDK |
Not really using, but |
Oh I see |
File removed |
@lexor90 well, simply because this is the official one 💁 |
I know, but if the latest version is broken and there’s a fork to patch it, as long as you can verify what actually changed from the main version I think it can be a viable solution (especially when things are going to be merged probably). At least you don’t have to patch things locally meaning you will not be able to repeat the build process without repeating the same steps which is not really scalable. Btw, I just wanted to give you a quick workaround. |
Agree. In the case of my company is just that this is -- at the end-- just a workaround. And we feel that an organization such as Facebook should provide a stable solution. As I said in previous comments, specially for a feature like this one from where Facebook actually profits a lot of money. |
@koenpunt why delete the branch? What's the current solution? |
react-native link doesn't support the new xml format yet, so for now we save it in the old format