Application Persistence

[AdmnJ]

So a number of applications like web browsers for instance save bookmarks, extensions, ect. when we update them but some applications like Spotify for instance looses all persistence and settings, login date, ect. when it updates using the scoop installer. How do we handle persistence and is there a method that we could use for apps like Spotify, if it has to do with the portable nature of the bucket then maybe a new manifest for the "non-portable" bucket?

If I knew where to start on the issue I would have already started.

[rashil2000]

Spotify loses its data because we run its uninstaller. Maybe we should not run uninstaller during the update process.
/cc @sitiom

[AdmnJ]

That makes sense, is there a way to specify a different process for updating then uninstalling and reinstalling in the manifest?

[rashil2000]

Inside the manifest we can detect if it's an update command or an uninstall command. Accordingly we can write statements.

[AdmnJ]

As far as the spotify package goes I have deduced that removing the AppData\Roaming\Spotify\prefs file is all it takes to wipe an active login.... however that doesn't wipe the settings once you are signed back in so there are more files that should probably be persistent.

[sitiom]

Fix on #8535