Sentry version: Sentry 20.12.0.dev 0d924458
- Virtualization: kvm
- Operating System: CentOS Linux 8 (Core)
- CPE OS Name: cpe:/o:centos:centos:8
- Kernel: Linux 4.18.0-193.14.2.el8_2.x86_64
- Architecture: x86-64
I had searched the similar issues on the Internet. Unfortunately, I can’t found any possible solutions although quite many of same cases online.
I uploaded the project source map to my Sentry server and delete it before deploy to cloud.
I assume it will take the Sentry artifacts while issue happens, but the actual result is it refer to a 404 source map in my cloud server.
As you can see, the JS file and source map are uploaded.
To prevent I was missed configuring anything, I did referred to the Sentry source map troubleshooting doc.
Verify a release is configured in your SDK
Yes, the release tag is “release-20201215” and the source map are uploaded to “release-20201215”
Verify artifacts are uploaded
Yes, all the files are uploaded as screenshot above shown.
Yes, it is present as screenshot above shown.
Verify artifact names match
Yes, I already compare the rules listed with my own URL, it fits with the first case.
Verify artifact names match stack trace frames
Yes, match as the screenshot above shown.
Verify artifacts are uploaded before errors occur
Yes, always double confirm while tests on different solutions.
Verify your source maps are built correctly
Yes, check the webpack build logs as well, all files are uploaded successfully.
Verify your source maps work locally
Yes, verified, works as usual.
Verify your source files are not too large
Yes, check the screenshot above.
Verify artifacts are not gzipped
Yes, it is a json file.
Verify workers are sharing the same volume as web (if running as docker on premise)
Yes, they are sharing the same volume.
Check the link for docker config printed through command
I spent my whole day for solving this issue but still have no idea which part is wrong. Please give me a hand Do let me know any info needed.