Skip to content

API Service doesn't account for socket exceptions (shows generic errors always) leading to bad UX #36

@pranavkonidena

Description

@pranavkonidena

Expected Behavior

The app shows network error's if any instead of a generic error anytime an exception is raised.

Actual Behavior

The app always shows generic error i.e Error Occoured which is not helpful , leading to bad UX.

Steps to Reproduce

Try refreshing or launching the app without internet connectivity

Suggested Way Ahead

I would like the implementation of a custom EMS (Error Management System) with a stream and an enum for different error types. Can use the network interceptor once implemented for connectivity status (#35 )

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions