SourceMaps not uploaded when using EAS Build

[yolpsoftware]

Summary

In my project, the source map upload to Sentry worked flawlessly as long as I was using Expo Build. Since having switched to EAS Build, it does no longer work. Sentry reports that the source maps are missing.

With Expo Build, the source map upload was done using a postPublish task in the hooks part of app.json, as documented here. If I understand it correctly, postPublish is not supported by EAS Build, so you need to use the sentry-expo plugin. This seems to be missing in the docs: it is not clearly stated that the postPublish hook is only for Expo Build and not for EAS Build. The docs make it look like you need both the hook and the plugin.

So in my project there are both the postPublish hook and the plugin:

{
  "expo": {
    ...
    "hooks": {
      "postPublish": [
        {
          "file": "sentry-expo/upload-sourcemaps",
          "config": {
            "organization": "myorg",
            "project": "myproject",
            "authToken": "..."
          }
        }
      ]
    },
    "plugins": [
      "sentry-expo"
    ]
  }
}

However, it still does not work.

Where can I start to find the cause of the problem? The eas build output does not mention anything related to Sentry or source maps, so I'm not even sure if the sentry-expo plugin is working correctly.

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

iOS

SDK Version (managed workflow only)

44

Environment

expo-env-info 1.0.3 environment info:
System:
OS: macOS 12.3.1
Shell: 5.8 - /bin/zsh
Binaries:
Node: 17.8.0 - /opt/homebrew/bin/node
Yarn: 1.22.18 - /opt/homebrew/bin/yarn
npm: 8.5.5 - /opt/homebrew/bin/npm
Watchman: 2022.03.21.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
IDEs:
Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
npmPackages:
expo: ^44.0.0 => 44.0.6
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
npmGlobalPackages:
eas-cli: 0.52.0
expo-cli: 5.3.1
Expo Workflow: managed

Reproducible demo or steps to reproduce from a blank project

I will create a repro, but first I need to know how I can debug this - the docs do not seem to be very clear (see examples above). As soon as someone confirms that my general setup is correct, I will try to isolate the problem into a minimal repro.

[johnny-mcfadden-dailypay]

Also experiencing this issue with the same postPublish hook & sentry plugin under a managed workflow & eas.

[mcavaliere]

I'm having similar trouble with a build on EAS. I'm not seeing explicit failures, and I do see sourcemaps, but no commits are getting associated with the release when setCommits is enabled. I can't tell if the upload-sourcemaps script is even running, which would make sense since postPublish is an expo publish hook, not an eas build hook.

[yolpsoftware]

@cruzach could you please take a look at this? Is my setup basically correct, aka should it work in theory?

[yolpsoftware]

@cruzach @brentvatne @EvanBacon can you please confirm that this is still maintained? Meaning that if I take the time to put together a minimal reproducible demo, you take some reasonable time to try to fix it?

I'm asking because the last contribution seems to have been months ago, and it seems pretty obvious that this repo (at least the docs) need some work.

[brentvatne]

@yolpsoftware - which version of sentry-expo do you have installed in your project?

[yolpsoftware]

@brentvatne I'm using 4.2.0

FWIW, not sure if that's related at all, but I noticed that the docs say that @sentry/react-native is a prerequisite for sentry-expo. So I added that, it was not yet installed. Doesn't make a difference to the topic of this issue.

However, when ejecting the project, the @sentry/react-native dependency leads to duplicate symbols for arm64 errors, because of both

- RNSentry (3.4.3):
  - React-Core
  - Sentry (= 7.11.0)

and

- Sentry (7.11.0):
  - Sentry/Core (= 7.11.0)

both being present in Podfile.lock.

If this is not related, I can put it into a separate issue.

[brentvatne]

@yolpsoftware - can you share a link to a build page where the build succeeded?

[brentvatne]

@yolpsoftware - I just looked at your builds and saw the most recent successful build on Sunday, June 12, 2022 and it appears to upload sourcemaps to sentry as expected

[brentvatne]

my only suggestion right now is to make sure you init with the Sentry import from sentry-expo:

import * as Sentry from "sentry-expo";

if you import Sentry from @sentry/react-native instead then the source maps won't work as expected because the filenames in the error stack frames won't be remapped to account for how expo-updates works. I have tried reproducing an issue with sourcemaps and sentry-expo and cannot do so if it's installed as described in the documentation.

[yolpsoftware]

@brentvatne thanks for you help!

It now works again. Seems that we didn't use the right version ID when initializing Sentry:

  Sentry.init({ 
    dsn: '...', 
    enableInExpoDevelopment: true,
    debug: true,
    release: Constants.manifest?.revisionId,                // <=== here we used something else
  });

Not related to EAS after all. Seems we changed that at the same time we switched to EAS.

Sorry for the inconvenience caused!

[juspeeh]

If anyone comes across this thread. There has been an issue with eas build for android which is solved by updating sentry-expo to 5.0.3. Here are more details: https://forums.expo.dev/t/eas-build-does-not-execute-postpublish-hook/66790

[orbiteleven]

@yolpsoftware Just coming across this thread with a similar issue. Can you clarify a few things?

1. Where are initializing Sentry?
2. Are you also using expo-updates, and if so do you have problems with Constants.manifest?.revisionId being empty?

Thanks!

[yolpsoftware]

@orbiteleven

1. in the App.tsx, i.e. one of the first calls.
2. we have expo-updates installed but we do not currently use EAS Publish or Expo Publish or whatever it is called (publishing OTA updates)

[felix-lambert]

I still struggle in uploading the sourcemaps from sentry. I'm using a bare workflow project and with eas build the sourcemaps are not being uploaded. Is there a workaround?