Purchase acknowledgment mismatch and purchaseState always null

[vikash92r]

Please use the Discussions board for questions or help. Use Issues strictly to report bugs.

I’ve integrated purchases through the Store API. After making a purchase and calling acknowledge from the backend:

• isAcknowledgedAndroid is returning true

• but isAcknowledged remains false

• Additionally, purchaseState is always null, which makes it difficult to determine the current state of the purchase

Steps to Reproduce:

2. Make a purchase.

3. Call acknowledge from backend using the Store API.

Inspect the purchase object.

Expected Behavior

• isAcknowledged should reflect the correct acknowledged state (not just isAcknowledgedAndroid).

• purchaseState should return the proper purchase state instead of null.

Actual Behavior:
• isAcknowledgedAndroid == true but isAcknowledged == false.

• purchaseState is always null.

[hyochan]

@vikash92r Could you kindly specify your environment and the version of sdk and any other details that may be helpful?

[vikash92r]

I am testing on Android, and I have noticed this in both flutter_inapp_purchase: ^6.6.1 and flutter_inapp_purchase: ^6.6.0

[vikash92r]

I have also noticed purchase.originalJson is also coming null but I am getting details in purchase.transactionReceipt

[hyochan]

@vikash92r I am currently stabilizing things in #555! I'll get back to you soon

[hyochan]

@vikash92r Would you like to try the version 6.7.0 which I am working on in #555? I did most of the migration

[hyochan]

Purchase no longer exposes shim getters like isAcknowledged or originalJson. The OpenIAP model already carries the source-of-truth properties:

• Use purchase.isAcknowledgedAndroid (or the new purchase.isAcknowledged once you’ve mapped it yourself) to check acknowledgement status.
• Use purchase.dataAndroid for the raw Play Billing JSON blob.

@vikash92r Also, #555 will be released soon to 6.7.1 and please feel free to tell when you still need assistnace