Skip to content

Suggestion to change Sentry.flush behaviour to resolve instead of reject for not initialized client. #3031

Closed
@vdanchenkov

Description

@vdanchenkov

Is far as I understand it's normal to not call Sentry.init in development env. Sentry.captureMessage and Sentry.captureException methods tolerate it and do nothing when called.

When deployed to AWS you have to call await Sentry.flush(n) (as suggested in many guides) to make sure that all data is sent, but this code throws exception if Sentry was not initialized.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions