Migrating UWP/DesktopBridge app to WinAppSDK Desktop

[JosHuybrighs]

There are currently 2 major issues when an existing UWP/DesktopBridge app/package on the Microsoft Store is migrated to a WinAppSDK desktop app/package and the 'new' package is published in the Store.

1. Background tasks that were registered in the 'old' package are deregistered after the update and can only be registered again when the user opens the app (where the app then checks registration and registers the tasks if necessary). I have no idea why the tasks are deregistered but I assume that this is because in the 'old' version all tasks were InProc tasks where in the new version they are OOP.
2. The windows.updateTask defined in the manifest file of the updated package doesn't run on the user's computer when the 'old' (uwp/desktopbridge version) is being updated (manually or automatically). I was hoping that if the UpdateTask would run I could re-register the above background tasks, but unfortunately I can't.

This leaves me with a big problem that my app, which is a files and folders sync/backup tool that mostly runs in the background (every 15 minutes), will be inactive as long as the user hasn't opened it. The user will typically not be aware of the update and therefore will not know that the sync/backup tasks are not being executed.
There doesn't seem to be any possibility to warn the user that he/she must open the app to get everything back to normal.

I have posted an issue (see #3250) about this, but the only reaction I got is that the issue has been assigned the Documentation label. This seems to indicate that one has to live with this.

What should I do then? Isn't this a serious issue for people who want to migrate an existing UWP app to a WinAppSdk app?