Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce auto source map uploading at build time #39

Open
jennmueng opened this issue Jun 2, 2021 · 4 comments
Open

Introduce auto source map uploading at build time #39

jennmueng opened this issue Jun 2, 2021 · 4 comments

Comments

@jennmueng
Copy link
Member

Most likely we would integrate the existing Sentry Webpack plugin

@muuvmuuv
Copy link

This would be spectacular! Just started using Sentry and was about to add a post build script. Since we are at an early stage, I can wait for this automation. Big love for your work into this!

@bruno-garcia bruno-garcia added this to To do in kanban via automation Jul 14, 2021
@bruno-garcia bruno-garcia added this to Backlog in Mobile Platform Team Archived via automation Jul 14, 2021
@bruno-garcia bruno-garcia changed the title Introduce auto source map uploading on build time Introduce auto source map uploading at build time Jul 14, 2021
@bruno-garcia bruno-garcia added the enhancement New feature or request label Jan 11, 2022
@lucas-zimerman
Copy link
Collaborator

When implementing this feature, it should also address this issue: getsentry/team-mobile#3

@muuvmuuv
Copy link

So we used the Webpack Plugin till now and it came to some problems with it after the build since the content hash on scripts differ between web and native build (two different pipelines on different providers...). I guess this would solve this because it would upload sourcemaps specifically for the native build. At the end it would mean three sourcemaps beeing uploaded; android, ios and web. Tagging these with some flag could help identify the build later in Sentry and match with its uploaded sourcemap.

@github-actions
Copy link
Contributor

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
kanban
To do
Development

No branches or pull requests

5 participants