Microsoft Store release updates may fail

[ZFordDev]

Summary

Updates for the SnapDock Microsoft Store release may currently fail. We are aware of the issue and are actively investigating a fix.

Affected release

• SnapDock 3.3.1
• Microsoft Store installation on Windows

Expected behaviour

Microsoft Store installs the latest available SnapDock update successfully.

Actual behaviour

The Store-managed update may fail to complete. Existing SnapDock installations remain usable.

Status

Investigation is in progress. User-facing notices have been added to the repository README and website downloads page.

[ZFordDev]

Update

For anyone following this issue: after some investigation, I think we've found a path forward for fixing updates on the Microsoft Store build of SnapDock.

SnapDock was always intended to let the Microsoft Store handle updates for Store installations. However, due to the complexity of producing the required MSIX package, we fell back to SnapDock's traditional in-app updater.

We've now found a promising way to automate MSIX packaging as part of the release workflow, which should allow Store builds to return to using the Microsoft Store's native update system as originally intended.

Testing is underway now. Assuming everything continues to work as expected, the fix should be included in an upcoming release.

Thanks to everyone following the issue and for bearing with us while we get this sorted.

[ZFordDev]

Update

Automating the MSIX workflow is currently blocked due to account-level permissions on my Microsoft account.

While I work on a fix for the account issue, I've adjusted the build process:

• Manual MSIX Packaging: Made it much easier to generate and manually submit MSIX packages directly to the Microsoft Store.
• Updater Behavior: Store builds have been switched to ignore SnapDock's built-in updater and defer entirely to the native Windows Store updater moving forward.

Note: The built-in Electron updater introduced in v3 has its own clunkiness, which will be tracked and addressed separately in #254.

I'll post further updates here as soon as the account automation issue is resolved.