Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
pranavkonidena opened this issue Feb 19, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@pranavkonidena
Copy link
Member

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 )

@pranavkonidena pranavkonidena added the enhancement New feature or request label Feb 19, 2024
@pranavkonidena pranavkonidena moved this to Todo in Mobile Dev Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

2 participants