[claude]

Requested by Ian Rumac · Slack thread

Changes in this pull request

Before: StoreTransaction.originalTransactionIdentifier reported the current transaction's own Google Play order id. For subscription renewals Google Play appends a recurrence suffix to the order id (GPA.1234-1234-1234-12345..0, ..1, ..2, ...), so a renewal reported an id like GPA.1234-1234-1234-12345..2 as its "original" transaction id instead of the first period's id.

After: originalTransactionIdentifier reports the base order id (GPA.1234-1234-1234-12345) by stripping the trailing ..N recurrence suffix, matching how the server side already normalizes these ids. Fields that represent the current transaction (storeTransactionId, EntitlementTransaction.transactionId, the redeem request's orderId) are unchanged.

How: Added an internal GoogleBillingPurchaseTransaction.originalOrderId(orderId) helper that strips a trailing ..N (\.\.\d+$) and applied it at the two sites that map a Play order id into an original-transaction field: the Purchase constructor in GoogleBillingPurchaseTransaction.kt and the TransactionReceipt.originalTransactionId collection in ReceiptManager.kt. Unit tests in GoogleBillingPurchaseTransactionTest.kt cover no-suffix, ..0, ..1, multi-digit ..12, single-dot ids that must not be truncated, and null.

Checklist

• All unit tests pass.
• All UI tests pass.
• Demo project builds and runs.
• I added/updated tests or detailed why my change isn't tested.
• I added an entry to the CHANGELOG.md for any breaking changes, enhancements, or bug fixes.
• I have run ktlint in the main directory and fixed any issues.
• I have updated the SDK documentation as well as the online docs.
• I have reviewed the contributing guide

---

Generated by Claude Code

[claude]

CI status on 3803111: all tests pass; the one red check is coverage-report, and it isn't this PR's code.

• unit-tests first failed because the Gradle wrapper download from services.gradle.org timed out before anything compiled (another PR hit the same timeout that minute). Re-runs passed, as did all five instrumentation-tests shards.
• coverage-report builds the report fine but fails at its "Commit coverage badge" step: GitHub rejects the bot's push to this branch with remote rejected ... (fatal error in commit_refs_rules). It failed the same way on two re-runs. The same bot push to this branch succeeded at 12:03Z today, so either a ruleset changed since then or it's a GitHub-side error. I can't read this repo's rulesets or branch protection from here (403), so someone with admin access would need to check, or re-run the job later.

---

Generated by Claude Code