Disable source maps upload without system wide env variable

[fbeccaceci]

Problem Statement

This screenshot is from Sentry docs https://docs.sentry.io/platforms/react-native/sourcemaps/

First thing i'd like to report is that the code showed for Android just doesn't work:

* What went wrong:
A problem occurred evaluating project ':app'.
> Could not read script '/Users/ipla/Dev/margelo/moto-app/sentry.gradle' as it does not exist.

I tried removing apply from: "../../../sentry.gradle" since that's already imported by the sentry config plugin and got this error

* What went wrong:
A problem occurred evaluating project ':app'.
> Could not find method sentry() for arguments [build_2xr5cs60tmkqb5bczn03j8eiu$_run_closure2@1cdb5ffb] on project ':app' of type org.gradle.api.Project.

---

Now, what i'm trying to achieve is to disable sentry source maps upload when building the app in release mode locally on my machine for testing or profiling.

I'm building the app for prod with EAS and that's the only place where the source maps upload should happen, so in the env variables developers can use locally the sentry auth token is not available and should not be, since it is used only in EAS builds where it is available.

This led local release builds to fail due to the source maps upload failing.

From your docs using SENTRY_DISABLE_AUTO_UPLOAD we can disable source maps upload, and that works, the only problem is that it only get's that from system env variables, which needs to be configured outside of the project globally since i often run the app through android studio and xcode to profile, which doesn't let me pass that env variable through command line.

Solution Brainstorm

Would be a good idea to have an option to pass to the sentry expo plugin that can disable source map upload.

That way it would be possible to set that option depending on .env file env variables or whatever other way one could want.

Are you willing to submit a PR?

None

[linear]

RN-413

[antonis]

Thank you for reporting and your suggestion @fbeccaceci 🙇
We will investigate this and iterate back!

[alwx]

@fbeccaceci
Regarding you not being able to import sentry in your android/app/build.gradle: could you please try that instead?

def sentryReactNativePath = ["node", "--print", "require('path').dirname(require.resolve('@sentry/react-native/package.json'))"].execute(null, rootDir).text.trim()
apply from: new File("${sentryReactNativePath}", "sentry.gradle")

sentry {
    // ...
}

---

Regarding env variables: There are actually multiple ways to approach that — for example, after applying sentry.gradle in your android/app/build.gradle you can simply override the function like that:

def sentryReactNativePath = ["node", "--print", "require('path').dirname(require.resolve('@sentry/react-native/package.json'))"].execute(null, rootDir).text.trim()
apply from: new File("${sentryReactNativePath}", "sentry.gradle")

// Override the shouldSentryAutoUploadGeneral function after sentry.gradle is applied
project.ext.shouldSentryAutoUploadGeneral = { ->
  // Your can write any logic here
  return System.getenv('SENTRY_DISABLE_AUTO_UPLOAD') != 'true'
}

sentry {
    ...
}

The same can also be done for iOS projects in Xcode — just take a look at sentry-xcode.sh and how it uses the SENTRY_DISABLE_AUTO_UPLOAD env variable internally. What's even easier is specifying the variables for a particular scheme, like that:

I hope it helps but let me know if you have any further questions.