Describe what happened
I'm not certain if this fits as a bug or if it might be a configuration issue on our side, but when using versionSuffix the logs will have the new version that will look something like "1.0.0-yourSuffix", the problem we have with that is that source maps seem to be uploaded with the version only, so "1.0.0", the consequence of that is that in error logs there is no sourcemap to get better trace of where the errror happened and a warning saying there is no sourcemap uploaded.
Steps to reproduce the issue:
Using the versionSuffix option in the config of the DatadogProvider
Describe what you expected:
Expect the uploaded sourcemaps to also use versionSuffix
Additional context
- We do have ["expo-datadog"] in the Plugins of Expo config and sourcemap are uploaded
- Version of the Expo SDK : 52
- Versions of
expo-datadog and @datadog/mobile-react-native
"@datadog/mobile-react-native": "^2.6.4",
"expo-datadog": 52.0.1
Describe what happened
I'm not certain if this fits as a bug or if it might be a configuration issue on our side, but when using versionSuffix the logs will have the new version that will look something like "1.0.0-yourSuffix", the problem we have with that is that source maps seem to be uploaded with the version only, so "1.0.0", the consequence of that is that in error logs there is no sourcemap to get better trace of where the errror happened and a warning saying there is no sourcemap uploaded.
Steps to reproduce the issue:
Using the
versionSuffixoption in the config of the DatadogProviderDescribe what you expected:
Expect the uploaded sourcemaps to also use versionSuffix
Additional context
expo-datadogand@datadog/mobile-react-native"@datadog/mobile-react-native": "^2.6.4",
"expo-datadog": 52.0.1