remote wipe doesn't wipe correctly and never finishes

EngelPika32 commented 2 years ago

So, I wanted to remote wipe my mobile to get rid of the old configuration and re-organize my file structure. Hence I did in the browser:

deselect "Allow filesystem access" for my mobile (to prevent messing with my files and block auto-upload)
select "Remote wipe" for your mobile (one day later, I decided to wipe it to create a new, clean, config for stuff like auto-upload)
The device is marked for a remote wipe but doesn't wipe itself. For comparison: My Tablet (Desktop-Client) did complete the wipe within a minute or so [marked at the same time]. Both devices were only before I marked them.

[days later]: notification "remote wipe started for -myMobile-" (finally). But… it never finished… [some days passed already again]

To conclude (Actual behavior):

The mobile device doesn't wipe itself (well, wipe all nextcloud data and caches; it's not a complete device wipe after all).
I can still see and navigate the cached file hierarchies
Occasionally the app shows me the login page (to enter the server address). However, with a simple "back button" press, I can go back. The App shows my account as login-ed…
Due to mass-login attempts the server eventually disabled my account (kinda funny…)

Expected behavior

all nextcloud data should be wiped from the device → cached files and cached folder hierarchies
it shouldn't be possible to view any previous screen (/ to navigate back from the login screen)
device should inform the server correctly about wipe start and wipe completed (Though, as the wipe didn't end 'correctly' this might behave correctly already…)

Can you reproduce this problem on https://try.nextcloud.com?

Didn't tried yet. I wanted to check back whether there might be some more useful information I could give here before I hard-reset the app. Additionally, I can't imagine any server setup preventing the remote wipe. It works with other devices fine after all.

Environment data

Android version: 9 Device model: H3113 Stock or customized system: stock Nextcloud app version: 3.18.0 Nextcloud server version: 21.0.7 Reverse proxy: caddy

Logs

Nextcloud log (data/nextcloud.log)

Just stuff like "Login failed for xxxx" (because obviously, the token isn't valid anymore).

AlvaroBrey commented 2 years ago

To clarify, you mean you triggered a remote wipe from google's Device Manager? Or was it some other software?

EngelPika32 commented 2 years ago

@AlvaroBrey Thanks for asking!

To clarify, you mean you triggered a remote wipe from google's Device Manager? Or was it some other software?

I triggered the remote-wipe in nextcloud (under /settings/user/security ). To be 100% clear, here an image:

SvenKoeck commented 1 year ago

Hi, I have the same problem: (too) many outdated entries, which are not deleted from my "device list" within nextcloud... has anyone found a solution yet? Or can give a hint...? Best regards Sven

hyprdrm commented 1 year ago

@EngelPika32 I have the same problem.

The client device is labelled “Marked for remote wipe” in Settings > Security > Devices & sessions, but it isn't actually wiped: access to the account is revoked - so the next time I open the sync client, it prompts for the server address and my user credentials - but all the files that have been sync'ed to local storage on the client are still available in the Android file browser 24 hours later.

Note: Devices & sessions gives me the option to revoke the wipe after I enable it. But it's not clear that this does anything(?)

@SvenKoeck Yes: I have multiple entries for the same device (which is confusing, and looks messy). But that feels to me like a separate issue, maybe(?)

Server

Nextcloud version: 24.0.8
Operating system and version: Ubuntu 20.04
Apache version: 2.4.41
PHP version: 7.4.3

Client

Android version: 13 (GrapheneOS)
Nextcloud Android client version: 3.23.1 (the official/stable app, not the dev version)

joshtrichards commented 8 months ago

Related issue in Server: nextcloud/server#38643

nextcloud / android