Closed petyots closed 1 year ago
Hello, thanks for the issue. As I can see from your code, your refresh token request only has a success callback and not a failure one. Have you tried to add a failure callback in which you can call the proceed(.continue) closure? Then you can catch the error from the caller. Let me know if this helps.
Issue is resolved for now by doing some changes on the backend. Will reopen if the solution of yours is needed and it does not work.
P.S Thanks for the great tool!!!
Hi, It seems there is an issue for which I can't find any workaround. I have UnauthorizedInterceptor which refreshes the access token when needed which is working fine.
BUT when the request which caused the token to be refresh also fails let's say with 422 in my case the Data is empty this is only happening when we are trying to catch the error in the request where 422 is happening
So when the interceptor is not involved everything is ok the
errorModel
is populated but when the interceptor kicks in the data is empty. Overall I think the request is throwing the error instead of passing it thru the interceptor that's why we can't catch the next error after the first(401) from the interceptor