You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is there an solution do handle errors globally. I have an app with an auth provider class, the auth provider hang on root of app. So if I can listen to parse errors in this provider, I can handle unauthenticated state and redirect to login state.
The text was updated successfully, but these errors were encountered:
Hey
You could probably create one yourself.
I think a repository style layer for all Parse data should suffice. Have
every call be sanity checked by a method which updates state. Every usage
of ParseObject requires a ParseResponse, so every return from the
repository layer could be something like return updateErrorState(response).
That way all errors are dealt with by this method?
On Tue, 3 Sep 2019 at 08:03, Alexander Buder ***@***.***> wrote:
Hi,
is there an solution do handle errors globally. I have an app with an auth
provider class, the auth provider hang on root of app. So if I can listen
to parse errors in this provider, I can handle unauthenticated state and
redirect to login state.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#265>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB4CPXX4V6HFWESP77OM2MTQHYD45ANCNFSM4ITCWOGA>
.
Hi,
is there an solution do handle errors globally. I have an app with an auth provider class, the auth provider hang on root of app. So if I can listen to parse errors in this provider, I can handle unauthenticated state and redirect to login state.
The text was updated successfully, but these errors were encountered: