I think this is an undocumented bug on keycloak side and affects developers using flutter app auth and keycloak. Someone needs to log it in github and add it to their backlog which consists of nearly 2000 bug tickets lol.

We have gotten around this by first initiating the delete action, then ignore all responses from keycloak and try to refresh user's token:

• if token refreshes, assume user cancelled flow

• if token refresh fails assume user is deleted - log them out