callstack / react-native-visionos

A framework for building native visionOS applications using React
https://callstack.github.io/react-native-visionos-docs/
MIT License
1.02k stars 30 forks source link

bundle exec pod install => ERR: No such file or directory #152

Closed saiuya closed 4 months ago

saiuya commented 5 months ago

Description

/Users//Library/Mobile Documents/com~apple~CloudDocs//code/RN/rnvisionos/node_modules/@callstack/react-native-visionos/sdks/hermes-engine/../../sdks/hermes-engine/utils/create-dummy-hermes-xcframework.sh


this path includes a space char, so can not find create-dummy-hermes-xcframework.sh file.

Steps to reproduce

when run command: bundle exec pod install

React Native Version

0.74.4

Affected Platforms

Build - MacOS

Output of npx react-native info

info Fetching system and libraries information...
(node:26456) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
System:
  OS: macOS 14.4.1
  CPU: (8) arm64 Apple M1
  Memory: 119.91 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 21.7.3
    path: ~/.nvm/versions/node/v21.7.3/bin/node
  Yarn: Not Found
  npm:
    version: 10.5.0
    path: ~/.nvm/versions/node/v21.7.3/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 21.0.2
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Stacktrace or Logs

info Fetching system and libraries information...
(node:26456) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
System:
  OS: macOS 14.4.1
  CPU: (8) arm64 Apple M1
  Memory: 119.91 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 21.7.3
    path: ~/.nvm/versions/node/v21.7.3/bin/node
  Yarn: Not Found
  npm:
    version: 10.5.0
    path: ~/.nvm/versions/node/v21.7.3/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 21.0.2
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Reproducer

https://github.com/callstack/react-native-visionos/

Screenshots and Videos

When Create your first App as "https://callstack.github.io/react-native-visionos-docs/docs/getting-started/create-first-app"


When it steps to "bundle exec pod install", I get this ERR message.

okwasniewski commented 5 months ago

Hey,

I couldn't reproduce your issue, can you create a project on a different path? Let's say ~/projects?

saiuya commented 5 months ago

Thank you for reply

I have put my project in another path, so that i resolved it。 However, when the path including a space, the create process will be in error, could you fix this issue?thank you。 Btw, created project makes vscode typescript server deactivate, i would give a tissue latter。

Yan

2024年7月2日(火) 23:20 Oskar Kwaśniewski @.***>:

Hey,

I couldn't reproduce your issue, can you create a project on a different path? Let's say ~/projects?

— Reply to this email directly, view it on GitHub https://github.com/callstack/react-native-visionos/issues/152#issuecomment-2203352937, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHP5EV63T2ZFEQNZ2TO7WBTZKKZJPAVCNFSM6AAAAABKF6MOKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBTGM2TEOJTG4 . You are receiving this because you authored the thread.Message ID: @.***>

okwasniewski commented 4 months ago

I'm not sure if react-native itself supports spaces in the path. I will double check that

okwasniewski commented 4 months ago

Hey @saiuya,

I've checked this and it works for me without issues. It may be something else.. not a space. Some special character?

saiuya commented 4 months ago

I put the project in Apple cloud before, so it contains a ~,maybe it is the reason!

2024年7月8日(月) 20:44 Oskar Kwaśniewski @.***>:

Hey @saiuya https://github.com/saiuya,

I've checked this and it works for me without issues. It may be something else.. not a space. Some special character?

— Reply to this email directly, view it on GitHub https://github.com/callstack/react-native-visionos/issues/152#issuecomment-2213789920, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHP5EVYAH57BEBDZV4EZ5D3ZLJ3TJAVCNFSM6AAAAABKF6MOKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJTG44DSOJSGA . You are receiving this because you were mentioned.Message ID: @.***>

okwasniewski commented 4 months ago

I've double checked looks like it was the space 👍🏻 Here is a PR to react-native which should fix it: https://github.com/facebook/react-native/pull/45316

saiuya commented 4 months ago

Hey @saiuya,

I've checked this and it works for me without issues. It may be something else.. not a space. Some special character?

okwasniewski commented 4 months ago

The fix was merged upstream and should be included in upcoming releases.