use_native_modules! skipped the react-native dependency 'react-native-unity-view'. No podspec file was found. in IOS only.

[marikani]

My react native version 0.60.5,Android is working fine.

[ziyoshams]

This is fine as long as you add the library manually.

[benjarwar]

Since 0.60 RN has moved to CocoaPods as default for dependency management. It would be best to add a Podspec for this project. @f111fei any plans to do so?

[benjarwar]

We are successfully using Pods to manage react-native-unity-view (we're using a forked version of this library, since it may be unmaintained; see #141).

For anyone interested:

1. Add a Podspec file at root of react-native-unity-view. You will need to adjust the s.source value to match your fork's location. We are using an add-podspec branch as per the below:

require 'json'

package = JSON.parse(File.read(File.join(__dir__, 'package.json')))

Pod::Spec.new do |s|
  s.name         = 'RNUnityView'
  s.version      = package['version']
  s.summary      = package['description']
  s.license      = package['license']

  s.authors      = package['author']
  s.homepage     = package['homepage']
  s.platform     = :ios, '9.0'
  s.ios.deployment_target = '9.0'
  s.tvos.deployment_target = "9.0"

  s.source       = { :git => '[https://github.com/******/react-native-unity-view.git]', :branch => 'add-podspec' }
  s.source_files  = 'ios/**/*.{h,m,mm}'

  s.dependency 'React'
end

2. Update package.json, adding a homepage attribute required by Podspec

  "homepage": "https://github.com/f111fei/react-native-unity-view/",

3. Fix the header search paths for RNUnityView after it is compiled as a target of your Pods project during pod install. This ensures that the Pods-managed version of RNUnityView can find files in the UnityExport directory as well as React dependencies. This is what works for us:

post_install do |installer|
  installer.pods_project.targets.each do |target|
    if target.name == 'RNUnityView'
      target.build_configurations.each do |config|
        config.build_settings['HEADER_SEARCH_PATHS'] ||= "$(inherited)"\
                                                         " $(PODS_ROOT)/../../node_modules/React/**"\
                                                         " $(PODS_ROOT)/../../node_modules/react-native/React/**"\
                                                         " $(PODS_ROOT)/../UnityExport/Classes"\
                                                         " $(PODS_ROOT)/../UnityExport/Classes/Unity"\
                                                         " $(PODS_ROOT)/../UnityExport/Libraries"\
                                                         " $(PODS_ROOT)/../UnityExport/Libraries/libil2cpp/include"\
                                                         " $(PODS_ROOT)/../UnityExport/Libraries/bdwgc/include"
      end
    end
  end
end

4. cd ios && pod install

Notes:

• If you have header/library/framework search paths to UnityExport files in your parent project, you can probably remove them as the Pods-managed RNUnityView will receive its own updated paths as per step 3 above.
• We found that once RNUnityView is managed by Pods, the target RNUnityView Xcode project in the Pods project of our Workspace did not preserve the header search paths set to the Xcode project in this project repository. Hence, the extra step to update the header search paths in the post_install hook.
• Make extra sure to avoid setting recursive header search paths to the UnityExport directory. We had done this while troubleshooting RNUnityView being unable to find UnityExport deps. And there are files, such as /UnityExport/Libraries/libil2cpp/include/icalls/mscorlib/System/String.h, that name collide with standard C++ library headers, causing builds to fail (often with hard to debug errors like 'limits' file not found)

[ziyoshams]

Awesome job

[benjarwar]

One more thing. On our CI, the Podspec wasn't passing validation because the description field in package.json passed to summary attribute in Podspec was an empty string. We fixed by updating package.json like so, from the README:

  "description": "Integrate unity3d within a React Native app. Add a react native component to show unity. Works on both iOS and Android.",

[marlon-wiprud]

Finally getting a chance to try out some of these solutions - thanks a ton for supplying the approach you took @benjarwar .

After implementing the above steps, I am running into this error: Property 'eventDispatcher' not found on object of type 'RCTBridge *'

wondering if anyone else has encountered this?

[ziyoshams]

@marlon-wiprud Any error that is related to React is your Header Search Paths for this package.

[benjarwar]

@marlon-wiprud can you send your ios/Podfile? Your React deps should all be managed there.

@ziyoshams is right, that the header search paths of RNUnityView will determine whether or not it can find React files. The problem is that CocoaPods works by accumulating all Podfile dependencies into a custom Pods project. In that process, header search paths set in this lib's RNUnityView.xcodeproj get nuked.

You can inspect what's set after running pods install by looking at the Targets listed in the Pods project in your workspace. So with Pods selected in the main nav, hit the dropdown or expand the project sidebar:

Select RNUnityView, and look at "Build Settings > Header Search Paths". You should see this:

[benjarwar]

Looking back at this, I think RNUnityView does not explicitly need to have React paths added once it's also managed using CocoaPods along with React Native. So these two lines can be removed from step 3 above:

                                                         " $(PODS_ROOT)/../../node_modules/React/**"\
                                                         " $(PODS_ROOT)/../../node_modules/react-native/React/**"\

We had remnants of getting Pods working in React Native < 0.60 in our Podfile, which required removing React deps from the Pods project within post_install hook.

[gustavobuttenbender]

Hi @benjarwar, thank you for the .podspec! I was able to pass through the .a files not being found; however, I got this error now in the Linking step of the build process, any chances you might have encounter it?

Not sure if I am missing something. I have made the link process manually:

• add RNUnityView.xcodeproj to the Libraries folder of my XCode Project;
• add libRNUnityView.a to the Link Binary With Libraries;

I have exported my unity project and added to ios folder, like this: ios/UnityExport.

I did not add the UnityConfig.xconfig file to XCode (not using it at all). Is it needed now that we are using CocoaPods?
I also do not have the UnityExport folder inside my XCode project, do I need to move it manually? If yes, should I also copy the resources?

Any help would be much appreciated. Thanks!

[ziyoshams]

@gustavobuttenbender Yes you need UnityConfig.xconfig because it contains needed flags for compiler. The thing you don't need is to link the library manually. Linking is taken care by podspec.

[gustavobuttenbender]

@ziyoshams Ok! Do you know how should I use the UnityConfig.xconfig with CocoadPods? Should I merge the .config into my PODS-{PROJECT_TARGET}.xconfig file?

[ziyoshams]

@gustavobuttenbender You don't do anything else with that file besides the steps in the docs.