Skip to content

pod install fails with latest canary #850

Closed
@tido64

Description

@tido64

Environment

System:
    OS: macOS 11.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 20.40 GB / 64.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.18.0 - /usr/local/bin/node
    Yarn: 3.0.2 - /usr/local/bin/yarn
    npm: 7.23.0 - ~/Source/react-native-test-app/node_modules/.bin/npm
    Watchman: 2021.09.06.00 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.11.2 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4
    Android SDK: Not Found
  IDEs:
    Android Studio: 2020.3 AI-203.7717.56.2031.7678000
    Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.12 - /usr/bin/javac
    Python: 3.9.7 - /usr/local/opt/python/libexec/bin/python
  npmPackages:
    @react-native-community/cli: ^4.10.0 => 4.14.0
    react: 16.13.1 => 16.13.1
    react-native: ^0.63.4 => 0.63.4
    react-native-macos: canary => 0.0.0-1d0b0891a
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce the bug

Use react-native-macos canary:

diff --git a/package.json b/package.json
index 15ac855..ac850c3 100644
--- a/package.json
+++ b/package.json
@@ -108,8 +108,7 @@
     "prettier": "^2.3.1",
     "react": "16.13.1",
     "react-native": "^0.63.4",
-    "react-native-macos": "^0.63.33",
-    "react-native-windows": "^0.63.32",
+    "react-native-macos": "canary",
     "semantic-release": "^18.0.0",
     "suggestion-bot": "^1.0.0",
     "typescript": "^4.0.0"

Run yarn and pod install.

Expected Behavior

pod install succeeds.

Actual Behavior

pod install fails with an error: : command not found

Reproducible Demo

git clone https://github.com/microsoft/react-native-test-app.git
npm run set-react-version canary-macos
yarn
cd example
pod install --project-directory=macos

Additional context

The reason for it failing is because of Windows newlines in scripts/ios-configure-glog.sh. The fix is to convert the file to Unix newlines.

Incidentally, have we considered publishing from a *nix VM to avoid issues with newlines and executable bits?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions