Repository navigation
Conversation
products create and update sent regionsVersion.version 2022/02. Under that version Bulgaria still expects BGN, so updating a product that is priced in EUR in Bulgaria (as the Console now prices it) fails with "Invalid currency for region code BG at the specified regions version 2022/02. Expected BGN but got EUR." Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
gpc products updatefails for a one-time product the Play Console has priced in EUR in Bulgaria:Bulgaria moved to the euro in 2026, but regions version 2022/02 still expects BGN there. The Console now prices products under 2026/01, and
products getreturns"regionsVersion": {"version": "2026/01"}for them. So a get, edit, update round trip can't succeed while the CLI sends 2022/02. #7 picked 2022/02 when it was the only version.This PR changes
products createandproducts updateto send2026/01. Nothing else changes.Testing: I built this branch and ran
products update --update-mask purchaseOptionsagainst a live product, using its full price list fromproducts get(174 regions) with only the US price changed. The 0.5.17 release failed with the error above. The patched build succeeded, and diffingproducts getbefore and after showed the US price as the only change.go test ./...passes.subscriptionsandoffersstill send 2022/02 and will probably fail the same way for EUR prices in Bulgaria. I haven't changed or tested them because I don't have a subscription to try against.🤖 Generated with Claude Code