-
-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xcode scripts should not use node
from path
#3472
Comments
Hi, We agree the The core of the issue comes from a misunderstanding I have tested the following code and loading the envs from
Thank you for mentioning the |
node
from path
Awesome looks like it will be fixed, I wasn't sure how my English was - it was 2am in the morning ;/ Just clarifying that you saying that I will leave my patch in until this issue is resolved. Looking forward to the fix! - let me know if you need me to test anything. Also, thanks for coming up with a better title :D |
Hi, I'm having the same issue. XCODE 15.1 and sentry/react-native 5.11.1 and I can't build using XCODE:
Will this PR fix this issue #3493? or do I need to fix it manually somehow? |
@Yuniac This seems like the path This was resolved in #3507 and is currently available in https://github.com/getsentry/sentry-react-native/releases/tag/5.16.0-alpha.4 You can also manually set the path to the |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 5.15.1
react-native
version: 0.73.0xcode
version: 15Are you using Expo?
Are you using sentry.io or on-premise?
Configuration:
(
@sentry/react-native
)I have the following issue:
Steps to reproduce:
Actual result:
Expected result:
For automatic scripts to work.
What I think is happening here is that sentry is making some incorrect assumptions to how WITH_ENVIRONMENT works.
And environments that do not have a default node installation breaks sentry's automatic scripts.
As environments that are managed by node version managers, i.e.
nvm
may not have a node in the pathFor context
xcode.env.local
While
with-environment.sh
does expose NODE_BINARY it does not put node on the path, and if node is not on the path when xcode runs the phase because we are using a node manager the sentry scripts will crashYou can actually fix the issue with
sentry-xcode.sh
withBy adding in the
$NODE_BINARY
in the script call.For
sentry-xcode-debug-files.sh
is a bit more tricky, while I'm not 100% on the cause but from reading the script the issue is the that when using the WITH_ENV script inside thesentry-xcode-debug-files.sh
it is isn't able to read the xcode.env which defaults toNODE_BINARY=$(command -v node)
which would require the system to have a default node.I got this working by, running the WITH_ENV script in the phase like so
Lastly, you are missing setting up the input files on
Upload Debug Symbols to Sentry
on the automatic installationThis will allow sentry to follow the same behavior that react native is following.
So TLDR:
The text was updated successfully, but these errors were encountered: