Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Android Developer: `productId` argument required inconsistency

Open
#32,796 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java
Domain
api, mobile

Research direction

The issue points to the AndroidPublisher.java file line 21976 where a precondition check on subscriptionId occurs. First, examine the generated client library structure and the API specification to understand the parameter requirement. Check if the method can be overloaded or the precondition relaxed. Running the provided code example will reproduce the error. Verify the fix by testing with a null subscriptionId as per the API docs.

Written by the indexing model from the issue text.

Description

hi!

in the Android Developer API, the purchases.subscriptions.acknowledge method has a subscriptionId path parameter, which the docs specify is not required and not recommended in some scenarios (docs link).

it seems the Java client library in this repo has a non-null precondition on subscriptionId, failing the request client-side (see code). should this be updated in the generated client library, either by overloading this method or allowing null values for this param?

Environment details

google-api-services-androidpublisher version: v3-rev20260909-2.0.0 (maven central)

Code example
client.purchases()
      .subscriptions()
      .acknowledge(appName, null, purchaseToken, requestBody) // throws precondition error
      .execute();
External references such as API reference guides
Dominant language
Java
Stars
725
Forks
394
Avg merge
45m
Merged PRs (30d)
240

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-api-java-client-services

All issues in googleapis/google-api-java-client-services

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.