Describe the bug

Errors in Sentry are being shown with invalid "unminified" (i.e. source mapped) stack traces. For example, with this error you can see that the minified stack trace and the unminified stack trace point at completely different places: https://metamask.sentry.io/issues/4887880395/events/4e5c635dce4a4b50b390fabaeaa38fd8/?project=2299799

Sentry maps these stack traces using the JS bundle and source maps associated with the release. This type of error usually means that the JS bundle or source maps uploaded as part of the release do not match the code being run in production.

So far I've seen this in v7.12.0 and v7.12.3. I don't know when it was introduced.

So far I've seen this on errors from Android. The few errors I looked at from iOS were less easy to decipher, I don't know whether they are being mapped correctly or not.

Expected behavior

Errors in Sentry should be mapped correctly, to the real source code that each minified stack trace line comes from.

Screenshots/Recordings

No response

Steps to reproduce

See the aforementioned Sentry link

Error messages or log output

No response

Version

7.12.0+

Build type

None

Device

Various devices, see the linked Sentry error

Operating system

Android

Additional context

No response

Severity

No response