OS:
Platform:
SDK:
@sentry/react-nativereact-native-sentrySDK version: 1.43.0
react-native version: 1.3.6
Are you using Expo?
Are you using sentry.io or on-premise?
I have following issue:
I am trying to set up my project so people can run Sentry from a dev environment, publish on app center and release on AppStoreConnect without having any risk to overwrite/reupload the sourcemap uploaded during production release.
By default "sentry-cli react-native xcode" creates a release named VERSION_BUILDNUMBER.
Steps to reproduce:
1- Release your app as 1.0 1000 in production
2- later a dev runs the same version in Xcode after doing some local changes - the dev overwrites the prod sourcemap because xcode Sentry build phase produces the same release name.
I don't know how to change the "sentry-cli react-native Xcode" build phase so it accepts custom release name?
Or maybe I am missing a Sentry feature allowing to block overwriting a sourcemap?
looking at the source code generating the release, the release name seems to be hardcoded:
https://github.com/getsentry/sentry-cli/blob/master/src/commands/react_native_xcode.rs#L266-L295
I don't understand how it could work with the function setRelease() in the SDK. setRelease() can not be used if we use the default Sentry command build phase generated by the Sentry wizard (this build phase will be called by a common Fastlane release which is calling xcodebuild)?
@HazAT I remember you said we should be using "sentry-cli reactnative xcode" instead of "react-native bundle" / "sentry-cli releases upload-sourcemaps" commands (https://github.com/getsentry/sentry-react-native/issues/790#issuecomment-602449313)
Can you explain what are the additional things done by "sentry-cli reactnative xcode" ?
It does look like that I would need to go back executing both of these commands but I would like to know what I am missing (but maybe I misread the "sentry-cli reactnative xcode" code - that would be better if I could change the release name from the build phase - so I would not have plenty of new code in my Fastfile :)).
We are wondering the same thing and have the same requirement (we need to specify release)
Can you explain what are the additional things done by "sentry-cli reactnative xcode" ?
Most helpful comment
@HazAT I remember you said we should be using "sentry-cli reactnative xcode" instead of "react-native bundle" / "sentry-cli releases upload-sourcemaps" commands (https://github.com/getsentry/sentry-react-native/issues/790#issuecomment-602449313)
Can you explain what are the additional things done by "sentry-cli reactnative xcode" ?
It does look like that I would need to go back executing both of these commands but I would like to know what I am missing (but maybe I misread the "sentry-cli reactnative xcode" code - that would be better if I could change the release name from the build phase - so I would not have plenty of new code in my Fastfile :)).