Skip to content
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.47.0-rc.2] Podspec: subspec "DevSupport" requires InspectorInterfaces #14975

Closed
HeEAaD opened this issue Jul 12, 2017 · 2 comments
Closed
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@HeEAaD
Copy link
Contributor

HeEAaD commented Jul 12, 2017

Is this a bug report?

Yes

Have you read the Bugs section of the Contributing to React Native Guide?

Yes

Environment

  1. react-native -v: react-native: 0.47.0-rc.2
  2. node -v: v8.1.3
  3. npm -v: 5.0.3
  4. yarn --version (if you use Yarn): 0.27.5

Then, specify:

  1. Target Platform (e.g. iOS, Android): iOS
  2. Development Operating System (e.g. macOS Sierra, Windows 10): macOS Sierra
  3. Build tools (Xcode or Android Studio version, iOS or Android SDK version, if relevant):
    Xcode: 8.3.3
    Cocoapods: 1.2.1

Steps to Reproduce

iOS project which tries to integrate React Native 0.47.0-rc2 with DevSupport via Cocoapods.

  1. have a package.json with React Native 0.47.0-rc.2 dependency
  2. run yarn install
  3. add the following lines to the Podfile:
pod 'React', :path => 'node_modules/react-native', :subspecs => ['BatchedBridge', 'DevSupport']
pod 'Yoga', :path => 'node_modules/react-native/ReactCommon/yoga'
  1. run pod install
  2. open the generate workspace
  3. try to build the project

Expected Behavior

Build will succeed without an error.

Actual Behavior

Build fails with the following error:

Undefined symbols for architecture x86_64:
  "facebook::react::IRemoteConnection::~IRemoteConnection()", referenced from:
      RemoteConnection::~RemoteConnection() in libReact.a(RCTInspector.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Reproducible Demo

https://github.com/HeEAaD/Demo-ReactNative-0.47.0-rc2-Podspec-issue
To reproduce the bug execute the folling:

  1. yarn install
  2. pod install
  3. open "ReactNative Podspec Dependency Bug.xcworkspace" with Xcode
  4. try to build it

Possible Solution

Add InspectorInterfaces to the DevSupport section of the React.podspec

  s.subspec "DevSupport" do |ss|
    ss.dependency             "React/Core"
    ss.dependency             "React/RCTWebSocket"
    ss.source_files         = "React/DevSupport/*",
                              "React/Inspector/*",
                              "ReactCommon/jschelpers/InspectorInterfaces.{cpp,h}"
  end
@javache
Copy link
Member

javache commented Jul 12, 2017

I think the correct solution is to add these files to the jschelpers_legacy podspec. Can you send a PR for this?

@HeEAaD
Copy link
Contributor Author

HeEAaD commented Jul 12, 2017

Sure, I'll create a PR.

HeEAaD pushed a commit to lovoo/react-native that referenced this issue Jul 12, 2017
HeEAaD pushed a commit to lovoo/react-native that referenced this issue Jul 12, 2017
HeEAaD pushed a commit to lovoo/react-native that referenced this issue Jul 12, 2017
ide pushed a commit that referenced this issue Jul 13, 2017
…pp,h}

Summary:
This PR fixes #14975.
* Podspec: add InspectorInterfaces.h/cpp to the "jschelpers_legacy" subspec.

1. lint the Podspecs: `./scripts/process-podspecs.sh`
2. check that an iOS project can integrate "DevSupport" via Cocoapods again. I'll already checked it on this branch of the demo project: https://github.com/HeEAaD/Demo-ReactNative-0.47.0-rc2-Podspec-issue/tree/fix
Closes #14988

Differential Revision: D5411733

Pulled By: javache

fbshipit-source-id: bb46cf3461e0857c7508264dafa204067af182c6
@facebook facebook locked as resolved and limited conversation to collaborators Jul 12, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants