Like onAppInstall and onAppUninstall, if you could provide an onSettingsSaved event, it could be used effectively.
Here’s my use-case:
On App Install, I create a recurring schedule.
On every subsequent “save” app settings, I need to delete the old recurring schedule and create a new one.
Because onSave is when I get the timezone information.
I will share some thoughts we took together, maybe your feedback will help us improve.
The runtime (afterAppUpdateHandler) will be invoked after the current installation (let’s say v2) is updated to v3. This means the authored code can depend on the new logic of v3 (may be in app.js or server.js, for example) in the execution context of v3’s afterAppUpdateHandler.
This also leaves us an open space in the future to invoke the beforeAppUpdate where the handler will be invoked before v3’s code is unpackaged. However, we are waiting for use cases to emerge to ship something like it.