How sentry incrementally uploads sourcemap in the same release (for when the micro-frontends base and the subapplication are released at different times) sentry 如何在处于同一个 release 下进行增量上传 sourcemap （针对于微前端 基座和 子应用发布时机不一致的情况下）

[Yangfan2016]

How sentry incrementally uploads sourcemap in the same release (for when the micro-frontends base and the subapplication are released at different times)
sentry 如何在处于同一个 release 下进行增量上传 sourcemap （针对于微前端 基座和 子应用发布时机不一致的情况下）

[lforst]

How are you currently uploading sourcemaps? Are you facing errors when uploading files using the Sentry CLI multiple times?

[Yangfan2016]

Our project is a micro front-end architecture, and the pedestal and subapps are built and published independently. The timing of the pedestal and subapps being uploaded to sourcemap is independent

However, in order to locate errors, I had to maintain release consistency, so I tried uploading both the base and the child application's sourcemap to the same release, but found that it didn't work

If you already have a sourcemap file under the same release, you won't be able to upload anything later

我们的项目是微前端结构，基座和子应用是独立构建发布的，基座和子应用上传sourcemap的时机都是独立的
但是为了定位错误，不得不维持 release 一致性，因此我尝试了把基座和子应用的sourcemap都传到 同一个 release 下，但是发现不可行
同一个release 下如果已经有sourcemap文件的话，后面上传的就传不上去了

[lforst]

Are you using Sentry CLI or the Sentry Webpack plugin? Also, are both microfrontends sending events to the same DSN?