Sentry show wrong stack trace

[tech-goldenphoenix]

Hello, my sentry issue shows the wrong stack trace. Could someone please guide me on how to fix it?

As we can see in the image. The line of code that Sentry point to is wrong (there is no .price). I checked my file and found it is another line of code. Btw, there is an error shown on the issue details. It says:

There was 1 problem processing this event
Source code was not found

The reason for it is the source code is from the old release. When I publish a new release for my website, the old file will be unavailable. I don't know if it related with the stack trace or not

Thanks in advance

[krystofwoldrich]

This seems to be the same issue as getsentry/sentry-react-native#3058

What do your release and dist look like? Do you have the same dist for iOS and Android? If so choosing a different dist for each platform/build will solve the issue.

[tech-goldenphoenix]

@krystofwoldrich The website uses a single distribution for all devices, and I am using Vuejs with Vite and @sentry/vite-plugin. However, I have encountered some issues where the wrong stack trace is displayed, while others show the correct one.

[krystofwoldrich]

I'm sorry I thought you are using RN app, I'll move the discussion to sentry-javascript.

Are you uploading source maps with debug ids? @lforst @Lms24 What could cause this?

[tech-goldenphoenix]

I do not manually upload source maps. The plugin @sentry/vite-plugin does it for me so I don't know if it adds debug ids along with source maps

[lforst]

@tech-goldenphoenix Can you share more information about your setup?

• What bundler are you using?
• What Sentry tool are you using to upload sourcemaps? Sentry CLI? @sentry/vite-plugin? @sentry/webpack-plugin?
• Did this suddenly regress for you? Was it working before?
• Is the code that is shown actually part of your code-base?

[lforst]

Is it possible to view the source code and the source map files that Sentry are using to show stack trace?

Yes go to your project settings under the sourcemaps settings and then "artifact bundles".

[tech-goldenphoenix]

I found a way to debug. I checked the release details on Sentry and found the exact version of my app corresponding to that release.
I rebuilt the source file with this tool. If you wanna try it on your own. Here are the js and the source map file. Then I searched for campaignDiscount: null and found that it points to the wrong source map code.

I checked out to the commit of that version and then built my project locally. After that, I checked with the source map tool again and it showed the same result. I tried to remove the vite-svg-loader and rollup-plugin-analyzer plugins and still got the same result, wrong source code position.

Then I checked out to the latest commit and build my project. When I checked with the source map tool, it showed the correct source code position. So I assume that the issue does not come from the plugins but comes from my source code.

But I don't know what to do next to find out which code causes the error. Do you have any suggestion?

[lforst]

Are you somehow manually transforming the js files after they have been built with vite?

[tech-goldenphoenix]

I think it's impossible because I use the CICD process to deploy my app to Google Cloud. All the build and deployment processes are controlled by Google Cloud build

[tech-goldenphoenix]

And I can reproduce the issue locally by checkout to the commit and building the project