Update Jumping Bytes PureSync Personal to version 8.6.0

[Christoph Güntner (JumpingBytes)]

📖 Description

✅ Checklist

• Signed the Contributor License Agreement
• Linked to an issue (if applicable)
  • Resolves #[Issue Number]

📦 Manifest Checklist

• Checked that there aren't other open pull requests for the same manifest update/change
• This PR only modifies one (1) manifest
• Validated manifest locally with winget validate --manifest <path> (validation guide)
• Tested manifest locally with winget install --manifest <path>
• Manifest conforms to the 1.12 schema

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

Microsoft Reviewers: Open in CodeFlow

[wingetvalidator-prod]

Found duplicate pull request(s)

• Manifest Path: manifests/j/JumpingBytes/PureSync/Personal/8.6.0
  • New version: JumpingBytes.PureSync.Personal version 8.6.0 #425058

[Christoph Güntner (JumpingBytes)]

I have no idea why the installation fails in the autmated test enviroment
The switch
ElevationRequirement: elevationRequired
is set in JumpingBytes.PureSync.Personal.installer
and the installer is run with these comand line options:
/exebasicui /qb /log ..
(when I run winget install --manifest ..)
I assume in the test enviroment they should be the same.

So, can either some provide me the log file of the installation (I ccannot fid it here)
Or look into that what the issue is, e.g. what uder dialog is shown

[Stephen Gillie (stephengillie)]

Automatic Validation ended with:

No logs after 5 retries.

(Deterministic automation - build 1811.)

[Christoph Güntner (JumpingBytes)]

Automatic Validation ended with:

No logs after 5 retries.

(Deterministic automation - build 1811.)

Can you please tell me the exact command line options the installer is started with.
And the same for uninstallation please.

I still have no clue how to solve, with no further info.
"No logs after 5 retries" does not help at all.
the log parameter is provied correctly in theYaml file.

Thank you

[Stephen Gillie (stephengillie)]

Automatic Validation ended with:

No logs after 5 retries.

(Deterministic automation - build 1811.)

[Christoph Güntner (JumpingBytes)]

I got some help here:
#425665

And I have now fixed 2 issues and compiled and uploaded a new version.
New checkings are running now.

[Kaleb Luedtke (Trenly)]

Hello Christoph Güntner (Christoph Güntner (@JumpingBytes)),

During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches?

This can also happen when a dependency is missing. You can test based on the documentation.

Please investigate a fix and resubmit the Pull Request.

You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress.

Template: msftbot/validationError/installation/unattended

Same issue as before -

MSI (s) (04:30) [15:28:14:909]: Error: cannot register 64 bit component {56682158-4199-41A7-8F41-278EBB3F6EE9} on 32 bit system. KeyPath:

If you update the Architecture to x64 as suggested above it should switch the validation agent to an x64 agent.

[Christoph Güntner (JumpingBytes)]

ok, I see 2 problems:

1. the error message box: Will be no longer shown in the next installation, when silent install
   So, that should be fixed

2. MSI (s) (04:30) [15:28:14:909]: Error: cannot register 64 bit component {56682158-4199-41A7-8F41-278EBB3F6EE9} on 32 bit system. KeyPath:
   That file is set to be installed only on 64 systems, and that is working fine here on a Win 10 x86.
   So why is that installed here on the test system?

(the installaion and the product itself is 32 bit.)

[Christoph Güntner (JumpingBytes)]

ok, so last changes to my installation finally seems to have fixed the problem.

I downloaded the logs (https://cdn.winget.microsoft.com/artifacts/WinGetSvc-Validation-425099-6-artifacts.zip) to check for problems
But there a no logs. the folder InstallationVerificationLogs are empty. Why that?

I must say, all this here is a nightmare to me - took me some days to solve this - so many unclear things, no or false error messages, no links, .... Without chatgtp and the forum I would not have been able to do this at all.

Sorry for opening many PRs - I still do not know the steps how to use the same PR again.

Next step is to test 'winget upgrade Jumpingbytes.PureSync.Personal' when merging is done.
Although, why merge? The new yaml files should be used, no merging.

[KarbitsCode (KarbitsCode)]

Although, why merge? The new yaml files should be used, no merging.

What do you mean exactly?