New package: MegaDev.PLITCH version 2.10.8

[megadevgmbh]

Pull request has been created with komac v2.11.2 🚀

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-61-260959-20250528-1

[megadevgmbh]

@microsoft-github-policy-service agree company="MegaDev GmbH"

[megadevgmbh]

The PR has been marked as Validation-Unattended-Failed, however when following the steps from Testing a manifest, the installation process succeeds without any interruptions or problems:

Contrary to what it says in the console window, there was in fact no UAC elevation prompt from the installer. I think it just warns of that because the manifest file details it as elevatesSelf, which was auto-generated by the komac utility.
The shell window was launched without admin privileges of course.

Additonally, the installer type is Inno Setup, a well-known installer type.

[ItzLevvie]

@wingetbot run

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-61-260959-20250528-2

[ItzLevvie]

@wingetbot run

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-61-260959-20250529-1

[stephengillie]

Automatic Validation ended with:

Signature Update Failed. 2025-05-28 18:37:38.482 Exception message: CreateProcess failed; code 216. 2025-05-28 18:20:40.501 Exception message:

(Automated response - build 1058.)

[megadevgmbh]

The PR has been marked as Validation-Unattended-Failed, however when following the steps from Testing a manifest, the installation process succeeds without any interruptions or problems:

Contrary to what it says in the console window, there was in fact no UAC elevation prompt from the installer. I think it just warns of that because the manifest file details it as elevatesSelf, which was auto-generated by the komac utility. The shell window was launched without admin privileges of course.

Additonally, the installer type is Inno Setup, a well-known installer type.

Still fails. Is there anything wrong with the manifest files or can I try something else?
As mentioned above, following the official steps works just fine, so I don't know why it would fail to install unattended in the pipeline...

[ItzLevvie]

Azure Pipelines is complaining about x86 OS but the application works only on x64:

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-63-260959-20250606-2

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-63-260959-20250606-3

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-63-260959-20250606-4

[microsoft-github-policy-service]

Hello @megadevgmbh,

The package manager bot determined there was an issue with installing the application correctly. Please check the application installs correctly. Once repaired, please push an update to your pull request.

Template: msftbot/validationError/installation/general

[megadevgmbh]

@stephengillie Do you happen to have any more information on what's going on, why the pipeline keeps failing?
Apparently it also fails with different errors, sometimes it is Internal-Error-Dynamic-Scan and sometimes it is Validation-Installation-Error.

[stephengillie]

Automatic Validation ended with:

No logs.

(Automated response - build 1064.)

[stephengillie]

Automatic Validation ended with:

No errors to post.

(Automated response - build 1064.)

[microsoft-github-policy-service]

The check-in policies require a moderator to approve PRs from the community.

Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission.

Template: msftbot/requiresApproval/moderator

[microsoft-github-policy-service]

Validation has completed.

Template: msftbot/validationCompleted

[ItzLevvie]

Sorry about the spam. Those are automated through GitHub CLI.

[wingetbot]

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