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

🐛 [firebase_analytics] Measuring in-app purchases manually required by StoreKit 2 #8077

Open
ninjz opened this issue Oct 22, 2024 · 5 comments
Labels

Comments

@ninjz
Copy link

ninjz commented Oct 22, 2024

Apparently when supporting StoreKit 2 on iOS, in-app purchases cannot be measured automatically by the analytics SDK anymore. https://firebase.google.com/docs/analytics/measure-in-app-purchases#implementation

I can't seem to find a method for manually tracking IAP events. Are there plans on supporting manually logging this or is this already supported somewhere?

@ninjz ninjz added Needs Attention type: enhancement Implements a new Feature labels Oct 22, 2024
@mikehardy
Copy link
Collaborator

Apologies, I do not know - this might be something to ask directly on stackoverflow tagging it appropriately (firebase team offers support there) or through your normal firebase support channels as opposed to this repo

Whatever they suggest is what we could aim for here

@ninjz
Copy link
Author

ninjz commented Oct 22, 2024

I think it’s quite relevant as a feature request to this repo seeing as this would require additional method calls to the native SDKs to support this.

There are already calls to log non IAP purchases. This would be an extension as auto-logging of IAP events will not work with the deprecation of StoreKit 1.

I believe this would be required by anyone interacting Purchase SDKs and need to send IAP purchase events back to Firebase analytics when StoreKit 2 becomes mandatory.

@mikehardy
Copy link
Collaborator

Totally agreed, the problem is I'm unsure what the native method calls are in the SDK and/or how firebase-js-sdk (our reference API) does it - do you have a link to their documentation and APIs / types for this perhaps

If not:

This might be something to ask directly on stackoverflow tagging it appropriately (firebase team offers support there) or through your normal firebase support channels as opposed to this repo

Copy link

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@github-actions github-actions bot added the Stale label Nov 21, 2024
@LectricAvenue
Copy link

@ninjz curious if you made any headway with this. I am about to start looking into this for a solution myself and figured I would check in here first.

@github-actions github-actions bot removed the Stale label Dec 3, 2024
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

4 participants