Repository navigation
fix(update): Store updates are offered whatever number comes with them, and the resident comes back after one - #94
Merged
Conversation
…umber comes with it, and says why it waits
…or a Store update, and for nothing else
…Store is asked once per half hour
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A copy from the Microsoft Store now offers the update the Store has, and the resident comes back by itself after the Store replaces it. This is the same fix Tisty shipped in its #580 and #582.
Why
StorePackageUpdate.Packagedescribes the package installed here, not the one coming, so its number is never ahead of the running copy.from_the_shopthrew every Store offer away as not newer, without a word.What changes
displaycatalog.mp.microsoft.com, product9N9F7C8Q43KC, fixed market and language). Packages for another architecture are skipped. If the listing cannot be read, the signed feed stands in. Nothing is installed from either.updateUnanswered).RegisterApplicationRestartwith--hushed, limited to being closed for replacement (no crash, hang or reboot). Only the copy that stays as resident registers.PRIVACY.mdnames the catalog request and the feed that stands in for it, since a Store copy no longer only talks to the Store.lib.rsand the resident'smain.rsshrink, andoversized.txtfollows them.How it was checked
cargo testforlinkunbound-settings,linkunbound-shellandlinkunbound-win; clippy with-D warnings;cargo fmt --all --check;scripts/rules.sh.npm test(209),biome checkandtsc --noEmitinapp; markdownlint.shop::verdict,update::listed,update::ahead), with a test for each shelf against each thing that can be known.rgdevment.LinkUnbound-BrowserPicker_2.9.0.0_x64__kdjgfdc2rb3gc, which is what the parser reads.GetApplicationRestartSettings.Not checked: a real Store update. That needs a copy with this change installed behind a newer Store release. The update that delivers this change will not reopen the resident, because the copy being replaced is the old one.