You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
11:44:12 AM: Running /usr/local/bin/bazel info '--override_repository=tulsi=/Users/xyz/Library/Application Support/Tulsi/0.20220209.88/Bazel' 11:44:12 AM: Bazel command info:
/usr/local/bin/bazel info '--override_repository=tulsi=/Users/xyz/Library/Application Support/Tulsi/0.20220209.88/Bazel'
Exited with code 127
env: node: No such file or directory 11:44:12 AM: Failed to query information about the Bazel workspace. Bazel exited with code 127 [Details]: env: node: No such file or directory 11:44:12 AM: Was not able to extract the execution root from the workspace. This is a Tulsi or Bazel bug, please report. 11:44:12 AM: Failed to retrieve information about the Bazel workspace. This usually means that the contents of a BUILD file are incorrect or flags are missing. Read the message log carefully for details. [Details]:
The text was updated successfully, but these errors were encountered:
System information (Please provide as much relevant information as possible)
Describe the problem:
Tulsi fails to generate xcode project as outlined in this step
Provide the exact sequence of commands / steps that you executed before running into the problem:
I have all the tools installed and was able to build iOS examples a couple months ago. I don't remember if xcode has recently updated, but it's at version 13.4.1 now. And today I wasn't able to create the xcode project with tulsi. Tried rebuild tulsi with xcode 13.4.1 but didn't help.
Complete Logs:
Tulsi log:
11:44:12 AM: Running /usr/local/bin/bazel info '--override_repository=tulsi=/Users/xyz/Library/Application Support/Tulsi/0.20220209.88/Bazel'
11:44:12 AM: Bazel command info:
/usr/local/bin/bazel info '--override_repository=tulsi=/Users/xyz/Library/Application Support/Tulsi/0.20220209.88/Bazel'
Exited with code 127
env: node: No such file or directory
11:44:12 AM: Failed to query information about the Bazel workspace. Bazel exited with code 127 [Details]: env: node: No such file or directory
11:44:12 AM: Was not able to extract the execution root from the workspace. This is a Tulsi or Bazel bug, please report.
11:44:12 AM: Failed to retrieve information about the Bazel workspace. This usually means that the contents of a BUILD file are incorrect or flags are missing. Read the message log carefully for details. [Details]:
The text was updated successfully, but these errors were encountered: