Skip to content

[iOS] - Export sourcemap location env variable when Sentry detected#75

Closed
sidorchukandrew wants to merge 2 commits intoDataDog:mainfrom
sidorchukandrew:main
Closed

[iOS] - Export sourcemap location env variable when Sentry detected#75
sidorchukandrew wants to merge 2 commits intoDataDog:mainfrom
sidorchukandrew:main

Conversation

@sidorchukandrew
Copy link

@sidorchukandrew sidorchukandrew commented Dec 18, 2025

What does this PR do?

This PR adds exporting the sourcemap file location to the if branch where Sentry is present in the build phase. When Sentry isn't present, it already adds this env variable export. This PR brings the Sentry case into alignment with when Sentry is not present

Motivation

Builds fail for us when we have expo-datadog and Sentry app config plugins.

I think this partly resolves this Sentry issue.

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests
  • Make sure you discussed the feature or bugfix with the maintaining team in an Issue
  • Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)
  • If this PR is auto-generated, please make sure also to manually update the code related to the change

When Sentry is detected in the shell script, DataDog
takes care to not interfere with it. Unfortunately, the DD CLI
fails because it can no longer find the sourcemap location. I'm
just copying the same sourcemap export present in the config
when Sentry is NOT detected.
@marco-saia-datadog
Copy link
Member

Thank you for your contribution! I have created a separate PR for this: #84. It will be merged and released soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants