Once Anytype uninstalled properly, it leaves data inside the Windows AppData folder. Especially a duplicate of the last installer, which is strange whether you uninstall it or not.
How to reproduce it
Steps to reproduce the behavior:
Uninstall Anytype properly through Windows Apps & Features
Check this two folders:
C:\Users\YOUR_WINDOWS_USER_ID\AppData\Roaming\anytype2
C:\Users\YOUR_WINDOWS_USER_ID\AppData\Local\anytype2-updater
📌 That’s a system folder that should be hidden and protected.
See for yourself that the uninstaller does not have completely uninstall.
Expected behavior
The uninstaller should not leave any data behind.
System Information
OS: Window 10
Device: Personal Computer
Anytype Version: 0.24.0
Additional context
I haven’t found a specific Bug report on this topic, but feel free to let me know if you know of one.
Most apps leave data behind even after uninstalling, especially in windows. These two folders however seems harmless and are useful when the app is installed again. One is the working directory which one can use to share the cached local media files to other devices if required.If one forgot to make a backup of it, they can do so now. Another is updater cache, this might not be usable to many. But for some reason, if one wants to reinstall the app after uninstalling, they can use this instead of downloading it again from the website.
On the other hand, the uninstaller could present an option to completely remove any traces of anytype from the device though. There is one more entry used by anytype that is IIRC is also not removed after uninstallation - the windows credential entry used to store the keyphrase. I’ll check this tomorrow and will update this post
Many developers no longer have the rigor of the past since the storage and computing power of the devices has become sufficient to not work in a clean and optimal way.
ㅤ
I don’t really agree, I think the term Uninstaller is explicit.
The app data folder will be deleting on uninstallation without confirmation. Confirmation is a little bit harder to implement.
This will be available in next release.
