Bring back transactionId

[Freddy03h]

Recently (I'm starting upgrade with 14.1.0), purchase.id is what was previously purchase.transactionId.

But now (14.3.7) on Android, purchase.id is a copy of purchase.purchaseToken

It's seems id is not a secure way to access a specific data, so, is it possible to bring back transactionId on Purchase to access this data safely?

Thank you.

[hyochan]

@Freddy03h Definitely! You just got same thought as I did which I've published the updates from 14.3.8. Sorry for the inconvenience.

Also, fyi https://www.openiap.dev/docs/types#purchase.

[hyochan]

I'll update the changes in next release but until 14.3.9 please use purchase.id which is now and orderId in Android which could be null. The only reason I think I should put back transactionId is because orderId is nullable in android which maybe confusing.

[Freddy03h]

Thank you for your answer!

In 14.3.9, purchase.id is back to transactionId on Android, but, as you say, I'll wait for transactionId back on Purchase.

--

Also, I experienced an other issue on iOS : purchase.transactionReceipt is now gone, the doc say to use purchase.purchaseToken for jwsRepresentation for iOS.

But the key doesn't look the same (not same char at the beginning of the chain than my stored receipt, and length is shorter) , and I can't validate the receipt on server. I receive 21002 error from Apple

The data in the receipt-data property was malformed or the service experienced a temporary issue. Try again.

Is purchaseToken on iOS supposed to be the same as transactionReceipt or I misunderstood?

[hyochan]

transactionReceipt is for storekit1 which library doesn't support anymore. We've shifted to Storekit2. PurchaseToken in iOS will return jwsRepresentation which is needed to validate StroeKit2 transaction

[hyochan]

@Freddy03h This can be closed via https://github.com/hyochan/react-native-iap/releases/tag/14.4.0