EKM error during logout? JWT no longer valid

[Kharchevskyi]

[tomholub]

Exactly when does this happen - what were the steps leading up to this? Are you able to reproduce it?

[Kharchevskyi]

today at 15:07 (gmt)
Was just trying to log out from account.
Have no additional logs because phone was not attached to debugger.
Was not able to reproduce today.

Will try to reproduce and add some logs

[tomholub]

The only time to call EKM is during setup.

Maybe it switched after logout to another account that was not finished setup. Then it tried to fetch keys during setup, but failed because the id token was too old (authenticated over an hour ago).

That would suggest that maybe code that clears accounts without keys is not working or is not being called at the right times (eg after logout but before switching to another account).

[Kharchevskyi]

I am using only one account at time.

[Kharchevskyi]

Will try to add logs if it occurs again

[tomholub]

I am using only one account at time.

That would mean one of two things:

• it calling EKM API when it shouldn't (during logout)
• it's somehow going through (parts of) setup flow when it shouldn't (during logout)

This error modal comes from thrown Error. Thrown errors should have call stack (I think). Please add a log to the generic API call error modal, so that every time any API error is rendered, it logs the call stack.

Even better, only on a debug build, it should also append the call stack to the modal message itself.