-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
searchPaths.filter is not a function, when unlinking #13160
Comments
my quick fix: |
@minhtc this worked for me. Thank you! |
@minhtc I didn't find this js file. Instead, I made all of the framework, header, and library search paths in |
+1 |
@mienaikoe Could you expand on that? |
hey @qruzz . It's been a while, but I think I remember what I was talking about: Somewhere near the bottom of the file, you'll have your build configurations. In here there are several build settings, including
Instead, as a workaround, you should make them into a list:
|
@mienaikoe Thank you very much for the reply ! |
Keep happening to me as well (0.46.4), anyone found a proper fix for it? |
@kelset Were you able to find a solution? Happening to me as well. |
@minhtc solution worked, but the file was at |
@ugiacoman sorry, not being able to fix it :/ Maybe with 0.48? I'll try to upgrade to latest once it comes out, let's see what happens then |
Same issue with react-native 0.49.1
|
I change the follow bit of code in the
to
and it seemed to have fixed the issue as well. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions. |
still there in 0.51.0 |
Confirmed on RN 0.51, when running
|
I'm also seeing this in RN 0.51 is the typical process to re-open an issue or create a new one? |
@pvinis, re-open please? And this obviously isn't |
Please re-open it. I also encounter this issue when I run |
After a bit of detective work (threw console.log statements throughout /node_modules/xcode/lib/pbxProject.js to see what part of the project file it was choking on) it seems like the installer was expecting my project to have a 'Plugins' group that I didn't have, I created an empty one in the project. My top level project groups now look like this: I also opened up ios/ and made sure that every variable that ended in *_SEARCH_PATHS was a list, it appears like xcode uses a string for single element lists, so I just wrapped parenthesis around those variables, after that I ran Perhaps the xcode library needs to be patched and/or there needs to be some exception handling for missing groups / lists that only have a single entry that are being treated as strings? |
can confirm this still happens in react-native 0.53! its neither stale nor fixed. Please re-open |
Saw now that the
New findings: it turns out that the offending package is not even from
|
This keeps happening and is not isolated to any particular library. I'm now on RN 0.54.4 and:
Re-open this. |
0.55.3 and it is still a problem, but as @pietro909 mentioned it appears to be a problem with a dependency, not React Native itself. The same basic fix from @minhtc still works with a few updates:
The current solution:
|
(cordova-node-)xcode 1.0.0 includes a fix for facebook#13160 plus a few more fixes. This should increase robustness in Xcode project handling overall. Fixes facebook#13160.
(cordova-node-)xcode 1.0.0 includes a fix for facebook#13160 plus a few more fixes. This should increase robustness in Xcode project handling overall. Fixes facebook#13160.
Summary: (cordova-node-)xcode 1.0.0 includes a fix for #13160 plus a few more fixes. This should increase robustness in Xcode project handling overall. Fixes #13160. ------------------------- Thank you for sending the PR! We appreciate you spending the time to work on these changes. Help us understand your motivation by explaining why you decided to make this change. If this PR fixes an issue, type "Fixes #issueNumber" to automatically close the issue when the PR is merged. _Pull requests that expand test coverage are more likely to get reviewed. Add a test case whenever possible!_ Pull Request resolved: #21766 Reviewed By: codytwinton Differential Revision: D10384245 Pulled By: hramos fbshipit-source-id: 488156be67cfc2d99ca81d7cb82747bab35984a7
Summary: (cordova-node-)xcode 1.0.0 includes a fix for #13160 plus a few more fixes. This should increase robustness in Xcode project handling overall. Fixes #13160. ------------------------- Thank you for sending the PR! We appreciate you spending the time to work on these changes. Help us understand your motivation by explaining why you decided to make this change. If this PR fixes an issue, type "Fixes #issueNumber" to automatically close the issue when the PR is merged. _Pull requests that expand test coverage are more likely to get reviewed. Add a test case whenever possible!_ Pull Request resolved: #21766 Reviewed By: codytwinton Differential Revision: D10384245 Pulled By: hramos fbshipit-source-id: 488156be67cfc2d99ca81d7cb82747bab35984a7
Summary: (cordova-node-)xcode 1.0.0 includes a fix for facebook#13160 plus a few more fixes. This should increase robustness in Xcode project handling overall. Fixes facebook#13160. ------------------------- Thank you for sending the PR! We appreciate you spending the time to work on these changes. Help us understand your motivation by explaining why you decided to make this change. If this PR fixes an issue, type "Fixes #issueNumber" to automatically close the issue when the PR is merged. _Pull requests that expand test coverage are more likely to get reviewed. Add a test case whenever possible!_ Pull Request resolved: facebook#21766 Reviewed By: codytwinton Differential Revision: D10384245 Pulled By: hramos fbshipit-source-id: 488156be67cfc2d99ca81d7cb82747bab35984a7
Description
i tried unlinking a library and i got an error
Reproduction Steps and Sample Code
try to link and then unlink a library i guess.
Solution
no idea.
Additional Information
The text was updated successfully, but these errors were encountered: