sentry-react-native: Issue with source maps and missing artifacts

Environment

How do you use Sentry?

• Sentry SaaS (sentry.io)

Which SDK and version?

• sentry-expo: 3.0.4
• @sentry/react-native: 2.2.0

Steps to Reproduce

1. Run my app (either via yarn ios or from within Xcode) – let’s say version 0.0.35, build 76
2. See a new release called 0.0.35 (76) in the Sentry project
3. Check the release and see that there are 0 artifacts

Expected Result

Artifacts would be available.

Actual Result

There are 0 artifacts in the release.

Setup information

I started my project as an Expo managed app and eventually ejected to the bare workflow.

Everything was working as expected (source maps and artifacts were available) while on @sentry/react-native version 1.9.0 but things broke when I upgraded to 2.1.0 and they haven’t been right since, regardless of what I’ve tried. Looking through the Source Maps section in Sentry, I last see a release with artifacts just before I did the 1.9.0 -> 2.1.0 upgrade but none since. Looking back at my changes then, I know I did something wrong – I started using:

import * as Sentry from '@sentry/react-native' instead of import { Native as Sentry } from 'sentry-expo'

Since then, I’ve resorted to using import { Native as Sentry } from 'sentry-expo' again after trying to debug this with somebody from Expo – I was told that I didn’t need to use sentry-expo as well as @sentry/react-native but that it’d give some extra features if I did.

Here’s some setup information:

sentryConfig.ts

import { Platform } from 'react-native'
import { Native as Sentry } from 'sentry-expo'

const SENTRY_DSN_IOS = 'xxx'
const SENTRY_DSN_ANDROID = 'xxx'

export const sentryConfig: Sentry.ReactNativeOptions = {
  dsn: Platform.OS === 'ios' ? SENTRY_DSN_IOS : SENTRY_DSN_ANDROID,
  enableAutoSessionTracking: true,
  debug: __DEV__ ? true : false,
  environment: __DEV__ ? 'development' : 'production',
}

App.tsx

import { Native as Sentry } from 'sentry-expo'

Sentry.init(sentryConfig)

// Sentry.captureException(error)

sentry.properties

defaults.url=https://sentry.io/
defaults.org=xxx
defaults.project=xxx
auth.token=xxx
cli.executable=node_modules/@sentry/cli/bin/sentry-cli

Xcode – Bundle React Native code and images

export NODE_BINARY=node
export EXTRA_PACKAGER_ARGS="--sourcemap-output $DERIVED_FILE_DIR/main.jsbundle.map"
export SENTRY_PROPERTIES=sentry.properties
../node_modules/@sentry/cli/bin/sentry-cli react-native xcode ../node_modules/react-native/scripts/react-native-xcode.sh
../node_modules/expo-constants/scripts/get-app-config-ios.sh
../node_modules/expo-updates/scripts/create-manifest-ios.sh

Xcode – Upload Debug Symbols to Sentry

export SENTRY_PROPERTIES=sentry.properties
../node_modules/@sentry/cli/bin/sentry-cli upload-dsym

Am I missing a manual step here or is there maybe an issue with my setup? I thought that when running/building a new version/build, a new Sentry release would automatically be created and everything would be handled. Here’s a screenshot of the Tags in a recent issue (from a release that has 0 artifacts):

I can see that dist is clearly taken from my build number and release is a combination of the version and the build numbers. This is clearly done automatically as I don’t set that explicitly anywhere.

The only way I’ve been able to create a new release and get artifacts/source maps is if I run expo publish manually. When doing this, I get a new release created but it has a name like 0.0.35-r.-DrbHnWJw and no issues seem to show up under that release. That release, however, does have artifacts, e.g.

whereas the automatically-created releases don’t:

Apologies for the length of this issue but I’ve been stuck with this for a while now and I wanted to give as much context as possible, hoping that it’s simply a setup issue on my side. Thanks in advance! Have a a nice day.