LifeCycle API: OnOverwolfExit or OnApplicationQuit(reason)

  • Feature Description:
    Add support for a life cycle event callback:
    onOverwolfExit (or OnApplicationQuit) - notify the app that Overwolf / App is closing down (user closed the OW process, or an unexpected shut down)

  • impact for my app: [low, mid, high, show-stopper].
    Mid impact

  • What is your current pain point?
    While we collect match data, OW might shut down resulting in data not properly managed.

  • What do you have in mind to solve it?
    Allow the app to register to an event that will be fired when OW is about to close down - allowing the app to respond.
    As an example, Unity has this callback when app is closing down https://docs.unity3d.com/ScriptReference/MonoBehaviour.OnApplicationQuit.html?_ga=2.84294041.1876949980.1583396039-1160785260.1566197742

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

@Eyal thanks,

We will update you here.

@Eyal is it still relevant? Can you please elaborate on why exactly do you need it?

It’s not my request, but here are a couple of use cases that I can think of off the top of my head:

  1. you’re sending data to your server indicating a user is in a game, relying on an event that tells you that the user exits the game at some point. User closes the app, event will never happen
  2. You have temporary data in memory that you want to flush to a db or storage at some point, but not immediately. User exits app before a triggering event - data is lost
  3. you want to track if user manually close the app after a game starts
  4. you created temporary data that you want to cleanup