Device trigger brute force protection when token is invalidated in the server

[CarlSchwan]

Steps to reproduce

1. Connect to a nextcloud server
2. In the nextcloud server, remove the token for the new android device

Expected behaviour

• The android device ask the user to log again

Actual behaviour

• The android device tries to reconnect and triggers brute-force protection

Environment data

Android version: unknow

Device model: unknow

Stock or customized system: I guess stock

Nextcloud app version: 3.18.0

Nextcloud server version: 20

Reverse proxy: unknow

[AlvaroBrey]

Reproduced with NC22 and app 3.18.0 in any emulator

[AlvaroBrey]

@tobiasKaminsky did we fix this? I tested it today with app&server master and it seems to work properly (login screen shows up)

[AlvaroBrey]

It seems like this was fixed at some point between 3.18.0 and 3.19.1, but I can't bisect to find the exact commit due to the snapshot dependencies in build.gradle.

@CarlSchwan Can you still reproduce this in current versions?

[github-actions[bot]]

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[AlvaroBrey]

Apparently bruteforce protection is still triggered if account is disabled entirely

[joshtrichards]

Duplicate of #9341 And related to #893