New version: CostaFotiadis.ADBExtensionforCommandPalette version 1.0.11.0

[CostaFot]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue? If so, fill in the Issue number below.
  • Resolves #[Issue Number]

Manifests

• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.12 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-142-375465-20260516-1

[CostaFot]

Thank you for your contribution @CostaFot! There was an issue validating your pull request. Many common validation questions and issues can be resolved by reading through the Validation Guide. Please review the guide and update your pull request if needed. If you have any questions, feel free to ask for help!

Template: msftbot/validation/validationGuideAdded

Hey hey, this looks like an arm64 runner timeout, the arm64 stage sat InProgress for like an hour before finishing. Can someone with validation re-run powers give it another go please? (@stephengillie maybe? 🙏 - Edit: it actually occured to me rather late that I can trigger re-run via empty commit)

Pipeline log (buildId 320717 https://dev.azure.com/shine-oss/winget-pkgs/_build/results?buildId=320717&view=logs&j=68997d86-8ece-5ae8-3ac5-ccdbfa458731&t=b79910ce-dca5-5e27-ad7f-bd285eecb5a2)

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-142-375465-20260516-2

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-142-375465-20260516-3

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-142-375465-20260517-1

[CostaFot]

Hmm I am a bit out of ideas. The Azure pipeline log shows only ##[error] Failed, with no specific error message.

I've verified the following locally for v1.0.11.0:

Downloaded both .msix files from the release URLs — both InstallerSha256 values match the manifest exactly.
Extracted AppxSignature.p7x from each — both SignatureSha256 values match the manifest exactly.
Both AppxManifest.xml files are well-formed (correct ProcessorArchitecture, Identity, Version 1.0.11.0, MinVersion).
The x64 MSIX installs cleanly via Add-AppxPackage on Windows 11 24H2 — no certificate or signature error.
winget validate passes

[stephengillie]

Automatic Validation ended with:

Signature Update Failed.
Installation failed with exit code -1978335216

Hex	Dec	Inverted Dec	Symbol	Description
8A150010	-1978335216	2316632080	APPINSTALLER_CLI_ERROR_NO_APPLICABLE_INSTALLER	None of the installers are applicable for the current system.

(Automated response - build 1368.)

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

[CostaFot]

Thank you @stephengillie !