Uninstall options that runs on Application uninstall

  • Feature Description:
    So this is a weird feature request, since the goal ofc is for users NOT to uninstall application from Overwolf. But if a user for some reason decided to uninstall the app it would be good if we could have some actions.
    I’m mainly thinking about apps that store data in %localappdata%. Currently if I decided that the application should store settings files etc in %localappdata% it would also be good if I could tell the app to also clear said folder on uninstall so that the end user don’t have “garbage” still on their computer.

But there could be other use cases as well. Like give the user a window during uninstall with a “Thanks for trying our product.”

Or for some reason the app has stored faulty values for some reason and the user tries a re-install it can clear said faulty files for a fresh re-install.

  • impact for all apps: low
  • What is your current pain point? No pain. Just good app practice to clean up after itself if removed.
  • What do you have in mind to solve it? It probably needs an addition to the actual overwolf client that reads from the application manifest being uninstalled if it has any commands to be run on uninstall.

You could also “lock” the app to only get write permission to a sandbox like %localappdata%/overwolf/apps/{appID}/ that gets created on install and on uninstall that folder gets removed. But you can still “read” files from the rest of the local filesystem like if you need to parse a games config file for hotkeys etc.

note for staff: after FR is accepted, add a link to the internal ticket.

Good idea but please don’t lock the write and read permission to a specific folder.
This can be very problematic for some apps.

Also, some users may want to keep the settings/data in case of reinstall so maybe we need a way to ask them before cleaning.

@uzi @StreamGameLabels it’s already in our backlog, although there is no ETA yet.

internal: bugz/issue/PLAN-262

@eransharv Yeah I guessed you’d already thought about it =) You can probably close this topic then.

@uzi I only mean the write could be locked to an app specific sandbox as I wrote above. Not being able to read some games configuration files etc could ofc be problematic, but do you need to write to anywhere on the filesystem?

// Joakim

@StreamGameLabels yes I’m :slight_smile: