Refresh JWT Token Interceptor in Flutter

[@emmalynnabiamos2412]

Thanks for this!

[@johndow618]

Why don't you use the 'expiresIn' parameter to determine whether you need to refresh the JWT before making a request to the server?

[@user-fo2jg2ln1n]

THANK YOU

[@matinrezaii3473]

Nice nice nice ! keep going

[@fasilaj857]

Q: If you are using the existing headers for the _retry function, the accessToken you are using is the expired one right?

[@ShakilAhmedPalatok]

I had exactly the same problem, after hours of failed attempt I found the bug. The solution is to add the new accessToken with the header and retry with the updated header

[@ntfnd4044]

it is good practice to use the QueuedInterceptorsWrapper

[@ronytesler]

But then you can't make calls in parallel, right?

[@subinsuresh]

How to handle parallel api request with expired token?

[@eggzzotic]

I agree this is a challenge I am wrestling with ATM also.

[@syfigaming4281]

Please, implemention in project

[@ulmasbekrakhmatullaev8808]

nice

[@ThinKingKaraoke]

How to use with GetX ?

[@codingdesign8312]

I refeshToken is Future and i call under onError function it auto many request , how i resoled , i use _retry function already

[@ShakilAhmedPalatok]

I had the exact same problem, your retry function is getting called with the same old access token, update your header with new access token and then retry using the updated header

[@johndow618]

To ensure that other requests wait until the token is refreshed (if necessary), you can use Completer. When the token update is complete, you'll call _completer.complete(), allowing other requests to properly send their request to the server with the updated token.

[@conceptcoder]

Hi Gabriel McReynolds, I already likes and subscribe your channel. Can I asking more about this topic with you. I really need your help/ advice about refreshing token with dio. Where I can reach you to ask more ?
Thanks.

[@tranong142]

Nọ, this is not best practice, because u can not handle to call multiple api when unauthenticated,

[@sojuz1204]

you mean handling multiple unauthenticated api calls at once?

[@tranong142]

​@@sojuz1204 yes, must have a mode for refresh token when the 1 refresh token is running.
EG: At once loaded:
request API 1 => unauthenticated => refresh token 1
request 2 (async with request 1) => unauthenticated => wait refresh token 1 response => use new token recall request 2
If i use your practice, request 2 will call new refresh token

[@tranong142]

@chau cao Mình code web FE nên trong thời gian refreshing mình sẽ đặt 1 cờ,
- Khi có unauthenticate mình sẽ check cái cờ đó trước, nếu có refreshing thì sẽ chờ request refreshing đó kết thúc và lấy luôn token mới của refreshing gọi lại api vừa unauthenticated

[@louisesandrinee.1882]

i think it's better to use instance of dio. and to create a class to extends interceptor

[@agungsubastian7384]

@@tranong142 is there any solution for this? I ran into this problem