Skip to content

Conversation

@aisgbnok
Copy link
Contributor

@aisgbnok aisgbnok commented Jan 23, 2026

Checklist for Pull Requests

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

@wingetbot
Copy link
Collaborator

Validation Pipeline Run WinGetSvc-Validation-128-333366-20260123-1

@aisgbnok aisgbnok force-pushed the new-Google.PlayGames-26.1.305.1 branch from ac74c9b to e65993b Compare January 24, 2026 19:36
@wingetbot
Copy link
Collaborator

Validation Pipeline Run WinGetSvc-Validation-128-333366-20260124-1

@microsoft-github-policy-service microsoft-github-policy-service bot removed Needs-Author-Feedback This needs a response from the author. New-Manifest Validation-Installation-Error Error installing application labels Jan 24, 2026
@wingetbot wingetbot added New-Manifest Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Completed Validation passed labels Jan 24, 2026
@stephengillie stephengillie added the Moderator-Approved One of the Moderators has reviewed and approved this PR label Jan 24, 2026
@stephengillie stephengillie merged commit 9640438 into microsoft:master Jan 24, 2026
1 check passed
@Kissaki
Copy link
Contributor

Kissaki commented Jan 24, 2026

How does this solve #326639?

@wingetbot
Copy link
Collaborator

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

1 similar comment
@wingetbot
Copy link
Collaborator

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

@aisgbnok aisgbnok deleted the new-Google.PlayGames-26.1.305.1 branch January 25, 2026 01:43
@aisgbnok
Copy link
Contributor Author

How does this solve #326639?

This corrects the version for the Google.PlayGames package from the incorrect version 144.0.7547.0 to the latest release version 26.1.305.1 based on ARP entry.

See #168014 for more details.

Because of the nature of the Google.PlayGames installer URL, wingetbot uses the wrong version numbers for Google.PlayGames. It needs to be manually corrected like in this case.

This resolves #326639 where version 25.12.11.2 was being prompted to update to nonexistent version 144.0.7547.0.

The problem is the URL used for the Google.PlayGames package. No one has yet to find and submit a static URL that is not encapsulated by the GoogleUpdater and supports silent installation.

Maybe a new issue similar to #168014 should be opened for the Google.PlayGames. Unfortunately, I'm not sure wingetbot can be updated to correct this. This is more of a validation pipeline issue where wingetbot's PRs should not be accepted because the version it's setting for the package manifest, in this case 144.0.7547.0, does not match the ARP entry after package installation.

@Kissaki
Copy link
Contributor

Kissaki commented Jan 25, 2026

I see, thank you for the elaborate explanation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Moderator-Approved One of the Moderators has reviewed and approved this PR New-Manifest Publish-Pipeline-Succeeded Validation-Completed Validation passed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Package Issue]: Google.PlayGames [Package Issue]: Google.PlayGames.Beta [Google.PlayGames.Beta version 25.7.774.0] Installer hash does not match

4 participants