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
There are no issues running the build from the command line, nor using the default react native bundling. The problem only occurs when integrating datadog to upload the bundlemap.
These logs are outputted:
Node found at: /Users/alex.curran/.nvm/versions/node/v20.5.0/bin/node
env: node: No such file or directory
Is datadog CI reading node from .xcode.env.local properly?
# This `.xcode.env` file is versioned and is used to source the environment
# used when running script phases inside Xcode.
# To customize your local environment, you can create an `.xcode.env.local`
# file that is not versioned.
# NODE_BINARY variable contains the PATH to the node executable.
#
# Customize the NODE_BINARY variable here.
# For example, to use nvm with brew, add the following line
# . "$(brew --prefix nvm)/nvm.sh" --no-use
export NODE_BINARY=$(command -v node)
Bug description
When following the instructions from https://docs.datadoghq.com/real_user_monitoring/error_tracking/mobile/reactnative/#alternatives-to-datadog-react-native-wizard-for-symbolication (or indeed the instructions for the wizard), making the required change to the "Bundle React Native code and images" step then results in the build consistently failing in Xcode with a node issue.
There are no issues running the build from the command line, nor using the default react native bundling. The problem only occurs when integrating datadog to upload the bundlemap.
These logs are outputted:
Is datadog CI reading node from .xcode.env.local properly?
Describe what you expected
Build script runs successfully in Xcode
Steps to reproduce the issue
Additional context
Node: 20.5.0
Xcode 16.1
React Native: 0.75.4
@datadog/datadog-ci: 2.42.0
@datadog/mobile-react-native version: 2.4.3
contents of xcode.env
contents of xcode.env.local
Command
react-native
The text was updated successfully, but these errors were encountered: