Clarification on Uploading source maps for updates

Expo Application Services (EAS)
1

I’m struggling with the documentation at Use Sentry - Expo Documentation

And specifically where it says

Copy or rename the bundle names in the dist/bundles folder to match index.android.bundle (Android) or main.jsbundle (iOS).

For android my dist/bundles has …

android-a293c5903e2dff6a980d753777d20206.js
android-a293c5903e2dff6a980d753777d20206.map

Should I copy them to…

dist/bundles/index.android.bundle.js
dist/bundles/index.android.bundle.map

or maybe…

dist/bundles/index.android.a293c5903e2dff6a980d753777d20206.js
dist/bundles/index.android.a293c5903e2dff6a980d753777d20206.map

Clarification would be much appreciated.

Dan

2

OK so it needs to be …

cp dist/bundles/android-*.js dist/bundles/index.android.bundle
cp dist/bundles/ios-*.js dist/bundles/main.jsbundle

and then sentry-cli will upload the source maps :slight_smile:

However, a sentry event isn’t happy and says e.g…

We’ve encountered 1 problem un-minifying your applications source code!
Dist Mismatch
The distribution identifier you’re providing doesn’t match. The dist value of dist configured in your Sentry.init must be the same as the one used during source map upload.

Currently I’m not setting “dist” in my Sentry.init() call, I just have …

Sentry.init({
  dsn: '<MYDSN>',
  enableInExpoDevelopment: true,
});

TIA

Dan

3

My bad, that example was for an app variant and I hadn’t used the correct package name in the sentry-cli upload.

All sorted now :smile: