Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No access to transaction when using paywall UI #4007

Open
5 tasks done
Jeehut opened this issue Jun 29, 2024 · 5 comments
Open
5 tasks done

No access to transaction when using paywall UI #4007

Jeehut opened this issue Jun 29, 2024 · 5 comments
Labels

Comments

@Jeehut
Copy link

Jeehut commented Jun 29, 2024

Describe the bug
I'd like to report successful purchases to an analytics service but it seems I have no access to the successful StoreKit.Transaction when I use the paywall UI features. When using my own paywall UI I get the transaction wrapped into a RevenueCat type which also has access to sk2Transaction to get the native StoreKit type. But the purchaseCompleted closure on paywall UI's does not contain a transaction. Please add one, it's lacking. Thank you!

@Jeehut Jeehut added the bug label Jun 29, 2024
@RCGitBot
Copy link
Contributor

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

@nyeu
Copy link
Contributor

nyeu commented Jul 3, 2024

Hi @Jeehut,

Thank you so much for your suggestion.
It makes sense to match the closures so we've added it to our backlog. I can't provide you with an ETA but I'll let you know when it's released.

Best,

@davidrothera
Copy link

Hey @nyeu is there any update on this? I suppose I could subscribe to transactions outside of my paywall flow however it would be easier to have this approach as proposed by @Jeehut.

🙏

@dpelletier2017
Copy link

Same thing, I have the exact same scenario as mentioned by OP, and I was also expecting purchaseCompleted to return a transaction.

Is there any news on this ?

@dlo
Copy link

dlo commented Nov 28, 2024

Is there a suggested workaround for this in the interim?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants