Skip to content

No error handling in background runners #155

@Random90

Description

@Random90

I had an error in my code, preventing it from scheduling notifications, but there was no errors in the logs and the worker job succeeded.
My code was failing silently.
I've tried using global try catch statement, but to no surprise, there was nothing passed to catch clause - error is undefined.

The only way to debug the code currently is to wrap it with multiple try catch statements to try to find the problem.

I don't expect a runner to have a whole call stack error handling provided, but at least some kind of basic message printed as a string in the logcat should be provided.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions