Skip to content

Capture errors for Replay that happen immediately after init #12707

@mydea

Description

@mydea

Today, we wait a tick to initialze replay (in replay-internal/src/integrations). This however leads to getsentry/sentry#72511 - we do not capture/assign errors that happen immediately after init was called.

We should find a way to make this work. Maybe we can just remove the timeout in the integration... 🤔 hard to say if there are any unexpected side effects there though...

Metadata

Metadata

Assignees

No one assigned

    Labels

    Package: replayIssues related to the Sentry Replay SDK

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions