QA checks:

• One account
• Two accounts in different servers
• Two accounts in the same server
• Three accounts in the same server
• Account switching
• Working after token renewal

(1) [FIXED]

I noticed the following effect in the current branch:

When the token expires and /konnect/v1/token is called to renew, the process is correct but the following request uses the expired token, causing un 401 and showing in the screen the snackbar dialog to re-authenticate. Just the following request, the following ones are OK and use the correct token. That means, user sees authentication is lost, bit it's not lost.

I realised that this 401 request is always a PROPFIND to /dav/spaces/... , that is expected but not sure...

After checking with master , it's not so reproducible as in the current branch. Also checked with two devices.

Maybe related with #4332

As required, this are the token request and response:

token.txt

and the request with the 401:

spaces.txt

As it is noticeable, the granted token in the first request is not the used token in the headers of the second one. Next requests are using the correct token.

When the tokes expires, the next request after /konnect/v1/token includes an Authorization header with the expired token. In this case, the header must be replaced with the new token. Therefore, the header replacement should only be applied if the request path is not /konnect/v1/token. I will update the code and let's see if it is fixed 🤔

Last update works pretty fine! 💯 . No more fake authorization lost messages. Checked that the following request to the token one is already using the new token. So, (1) is fixed.

Approved!