getsentry / getsentry/self-hosted

Vue Error that is detected in Issue not propagated/visible in Replay under Errors tab

Open
#3,086 17 comments 0 reactions 0 assignees View on GitHub
Bug
Dominant language
Shell
Stars
9.6k
Forks
2k
Avg merge
1d 3h
Merged PRs (30d)
12

Description

### Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

### Steps to Reproduce

1. Create a basic [Vue3 project ](https://vuejs.org/guide/quick-start.html) using npm create vue@latest ( Use "Yes" when it asks you for options )
2. Install sentry using the standard recommended config and don't use the tunnel ( Happens on Tunnel as well )
3. Change code inside App.vue. Replace script and template with this to create a simple error on click. ( something should throw an error inside updateBar() )
```js

import { RouterLink, RouterView } from 'vue-router'
import HelloWorld from './components/HelloWorld.vue'
import { ref } from 'vue';
const message = ref("WelcomeMessage");

function updateBar() {
message.value = new Date().toDateString();
const response = fetch("https://this-is-error-now.com");
}




{{ message }}


TestError


Home
About


```
4. Check Sentry Issues and Sentry Replay

### Expected Result

1. Sentry Issues -> New Issue is opened
2. Sentry Replays -> New replay is created with the TypeError visible on the Replay timeline and inside the "Error" tab

### Actual Result

1. New Issue gets created
![image](https://github.com/getsentry/sentry/assets/41236638/82e39b47-d573-4496-bb54-b4c9b5f654b8)
2. Replay gets created and Error tab is empty
![image](https://github.com/getsentry/sentry/assets/41236638/b89f4321-4702-4ae4-aa32-6c7ca5855506)
3. Trace with error exists
![image](https://github.com/getsentry/sentry/assets/41236638/d18c368e-fac3-4715-838e-f0b3682752cd)

### Product Area

Replays

### Link

_No response_

### DSN

_No response_

### Version

24.4.1

Contributor guide

Open the contributing guide

Research direction

Use the Vue 3 reproduction in App.vue, especially updateBar(), to generate the issue and replay. Compare the resulting issue, trace, and Replay Errors tab; done means the captured TypeError appears in the replay timeline and Error tab as expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.