Mar 29 2021 02:15 PM
Mar 29 2021 02:15 PM
I have a new UWP application that can be installed (side-loaded) from the web with a valid certificate. However so far during testing I am unable to get the app to update when a higher version number exists on the website when auto-update is set to "0" hours or any other condition I have tried. I am at a loss to troubleshoot the issue. If I attempt to update the UWP app manually over HTTP it works as expected and recognizes when the version is the same, newer, or even older. It even installs on Windows 10 machines not in developer mode as I had hoped. If I switch the app source to a local drive and test it acts the same. What exactly are the triggers on the Windows 10 PC that cause the updated version to be discovered? What should I be looking for?
- new to all this
Apr 13 2021 02:00 PMSolution
I'd like to offer some help to you on this. It sounds like you've selected to distribute your Windows App using an AppInstaller file (configured with automatic updates). Can you share a copy of your AppInstaller file that's being used to install / update your Windows App on client computers.
A couple key items to be aware of, the AppInstaller URI specified in the AppInstaller file must point to itself, and the AppInstaller file used for installing the Windows App must be updated to contain the newer version of the Windows App.
For more information, please also visit our Microsoft Doc's Article on AppInstaller and Auto Updating:
Apr 27 2021 04:45 PM
May 03 2021 04:30 PM
No worries about the delay, I'm happy to help. You can share your AppInstaller file with me directly via Tech Community DM. I've sent you a message, please respond to it with a copy of your AppInstaller file.
I would like to direct you to the AppInstaller Schema 2017 v2 that you are likely using with your AppInstaller file. More importantly the Auto Update settings (found by selecting the "OnLaunch" link).
|HoursBetweenUpdateChecks||HoursBetweenUpdateChecks specifies the frequency with which the the deployment service will check for an update to the App Installer file.||Numeric
|ShowPrompt||Indicates if deployment will show a prompt, informing the user about the update.||Boolean|
Should only be used if ShowPrompt="true". Indicates if deployment will stop the user from launching the application until the update has been applied.
“UpdateBlocksActivation” = true means the UI the user will see allows the user to take the update or close the app.
“UpdateBlocksActivation” = false means the UI the user will see allows the user to take the update or start the app without updating.
If your users are not receiving a prompt when an update is availabe as they are launching their Windows App, please make sure you've configured the above settings correctly.
Please note that AppInstaller setting changes are applied when the app is next updated or reinstalled.
If this has been helpful, or has answered your question please mark it as "Verified Answer".
May 08 2022 06:15 PM
May 10 2022 09:32 AM
Unfortunately, I do not have any updates on the "ms-appinstaller" activation protocol beyond pointing you to the blog post that described the problem. Dian has shared in the blog post that new updates will be shared in this blog post.
Please keep an eye on this blog post as an update will be posted.