Account stays logged in throughout reset

[Zthrowaway]

All the guides I have found have said that my account should be removed after reset. However, upon following the instructions, I am still logged in, and no matter how many times I've repeated disabling companion and resetting it's just not working. I don't have many details because I don't know what is causing the problem, and the only details I can offer at the current time that might be relevant are the following:
a) Oculess is the device owner. b) All account features are retained through the reset. c) Software Version: 41.0.0.124.268.379035663 d) Runtime Version: 41.0.0.124.307379035701 e) Oculess Version: 1.3.5 f) Has been tested with both WiFi off & on, as well as before and after the cache was cleared. f) This is on a Quest 1.

Edit: I've fixed this in a way. I boot with wifi off and use TrackerControl (From F-Droid) to block the system using WiFi. I can still use wifi on browsers (Have only tried with DuckDuckGo) and mostly use the internet (Works with Webtoon, not with QuestCraft) but I don't know if this disables the piracy switch and I can't use another tracking blocker, a VPN, or a DNS (Anything that requires the VPN capability) because TrackerControl takes that spot. I can also use my apps from the Store, so I'm not sure if that introduces any complications.

[GitEmulate]

Having the same issue, Quest 2 V42. I don't trust something like trackercontrol or a DNS to block everything, those block domains but won't stop direct IP connections (something Facebook is known to use). I really hope basti564 fixes this soon, I turned off my WiFi for now, but this means I can't use ALVR and I can't play multiplayer app lab games like Pavlov...

[basti564]

Hi, I will take a look what's wrong with it not removing accounts.
As far as the piracy killswitch goes it has never been fully implemented in a production release, so no need to worry about that.

[basti564]

It seems like Meta patched the method used by Oculess to disable the companion server in v42 (or v41?), I don't think I will be able to bypass this.