- Yes, we still have the Bundle Id configured in the Application ID > Apple page on brainCloud.
- Yes, we are still calling
CachePurchasePayloadContext()withitunesand thepayload. This code path hasn't changed as we've upgraded from5.8to5.9
peter
Posts
-
-
Thank you for the advice, we have now managed update our Application IDs.
However:
- We always get a
101Transaction id not foundfailure from Brain Cloud when attempting to verify an in-app purchase. - When
Use App Store Server API for legacy receiptsis checked, we also get a101failure when testing with older builds that use Brain Cloud5.8client and StoreKit1.- However, if we uncheck this, older builds transactions succeed as expected.
Given the fact we see the same behaviour on legacy transactions, I suspect this may be a fault on your side? If not, is there anything further I can do to investigate?
Notes on retrieving a transaction id with Unity.
We are using Unity IAP
5.1.2, it can be a bit confusing to find out where to retrieve theTransactionID, and not theOriginalTransactionID- as requested by the BrainCloud docs. (Though in my initial testing shows these ids are often the the same).Initially I parsed transactionID from the jws returned from the app store (a convoluted process), I then realised
PendingOrder.Info.Receiptreturns a json string which hasTransactionIDas one of it's fields.The data we submit to
VerifyPurchase()looks something like this:{"excludeOldTransactions":false,"transactionId":"2000001103879447"} - We always get a
-
I have tried following the instruction (triple checked I have found and copied the correct fields) but I keep getting a "Itunes Inapp Integration fields incomplete" error when I try to save the page.
I am supplying:
App id > id shown in general information
Issuer id > Copied from in-app purchasing integrations page
Key ID > Copied form in-app purchasing integrations page (for the specific key)
Encoded key: Contents of the p8 fileThe copied error message
---- CONTEXT ---- { "email": "redacted@redacted.com", "teamId": "redacted", "accountNumber": "redacted", "appId": "xxxx", "appName": "Redacted", "profileId": null, "page_path": "/", "page_search": "", "page_hash": "#/app/design/core-app-info/application-ids", "page_location": "https://portalx.braincloudservers.com/#/app/design/core-app-info/application-ids" } ---- DETAILS ---- { "errorCode": 2020000, "errorMessage": "Itunes Inapp Integration fields incomplete", "reasonCode": 40660 } -
Thanks for the update!
-
This is also a major blocker for us. We recently upgraded our laptops, which only support XCode 26. This meant we had to upgrade all of our dependencies, which forced us to migrate to Unity IAP v5 - so it's currently not possible for us to roll back to Unity IAP 4 (and therefore storekit 1).
Are there plans to support Storekit 2 receipt verification?
Are there plans to support Storekit 2 receipt verification?
Are there plans to support Storekit 2 receipt verification?
Are there plans to support Storekit 2 receipt verification?
Are there plans to support Storekit 2 receipt verification?