[iOS] [BUGFIX] Fixing error when using RCTAnimation in Swift project using cocoapods

[barrault01]

Hello,

When you try to install React Native with RCTAnimation dependency using Cocoapods on an existing swift project, it does not compile.

This PR fixed the problem explained in this issue :#13198.

The solution was already presented here: #13198 but never implemented.

Test Plan:

Clone this project that demonstrate the bug : https://github.com/barrault01/swift-reactnative.git

git clone https://github.com/barrault01/swift-reactnative.git
yarn install
cd ios
pod install
open ReatNativeSwift.xcworkspace 

To fix the bug update the version of react-native on the package.json

{
  "name": "MyReactNativeApp",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start"
  },
  "dependencies": {
    "react": "16.4.1",
    "react-native": "git://github.com/barrault01/react-native.git#70f7e5ea9ed226604d795b6646f14a8192b860fb"
  }
}

Then run do this again on the root folder of the project:

yarn install
cd ios
pod install
open ReatNativeSwift.xcworkspace 

And now the build will sucessed.

Release Notes:

[iOS] [BUGFIX] [Cocoapods integration] - now using RCTAnimation subspecs does not make the build failed on iOS when integrated React Native using Cocoapods.

[facebook-github-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

[pull-bot]

	Warnings
⚠️	❔ Base Branch - The base branch for this PR is something other than master. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on master first and then cherry-pick the commits into the branch for that release. The Releases Guide has more information.

Generated by 🚫 dangerJS

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[barrault01]

@react-linter I made this PR on top of the 0.57-stable because I would like this fixes to be on the new react native release it was around for such a long time and it needs to be fixed.

[barrault01]

@react-native-bot release note is available I think you missed it ;)

[hramos]

@barrault01 we don't accept PRs on anything other than master. Once a change lands on master, you can comment on react-native-community/releases#34 to request your changes be cherry-picked onto 0.57.

If we accepted PRs on stable branches, your changes would be limited to 0.57, and would not be available on 0.58, for example.

[Titozzz]

Great it’s the last sed I’m doing on postinstall 🎉

_{Sent with GitHawk}

[barrault01]

@hramos Thanks for the clarification, I reopened the PR #20963 can you give it a look?