Normally the updater window closes quickly after our app auto-launches after an update. When we enabled Installer Analytics, however, the updater window stays longer than usual, around 30 secs, after our app auto-launches. Disabling analytics, i.e. adding AI_IA_ENABLE="0" to the CommandLine in update.aiu, fixes the issue, but this is not desirable. Is it possible to hide the updater window while it's sending analytics data so it doesn't interfere with the already-launched app?
We're not really looking to hide the updater's GUI altogether, just the part where it's sending analytics data, w/c we assume happens at the end, past the point where update errors might happen. Is this not possible?
Another concern with hiding the updater's GUI is how errors are shown to the user. In case of an update error, the updater usually shows the error message on the updater window. How is this handled when the GUI is hidden?
First of all, are you able to replicate this on multiple machines?
I have tried testing this right now and I was not able to replicate the behavior you mentioned. Perhaps I was doing something wrong in my tests, so could you please give me a step-by-step test-case which I can use in order to reproduce this?
What I've done is basically:
- install V1
- add the AI_IA_ENABLE="1" for the command line in the Updates Configuration Project
- launch the updater to install V2
The second version was installed as expected and the updater seemed to close immediately.
Preconditions:
1. V2 has AI_IA_ENABLE="1"
2. V2 is set to launch the app in an upgrade scenario via custom action
Steps:
1. Install V1
2. Launch updater to install V2.
3. App launches after the update while the updater window stays longer.
In another test, we did the ff. and could not repro the issue.
1. Install V1
2. Add our custom property that disables tracking to update.aiu. This custom property internally sets AI_IA_ENABLE="0" via custom action.
3. Launch updater to install V2.
4. Updater window closes and then launches the app.