firebase-ios-sdk icon indicating copy to clipboard operation
firebase-ios-sdk copied to clipboard

Feature request: disable auto logging of in_app_purchase.

Open Igor-Poltavtsev opened this issue 6 years ago • 18 comments

It's needed a way to stop tracking in_app_purchase automatically collected event on iOS.

Igor-Poltavtsev avatar Feb 23 '19 02:02 Igor-Poltavtsev

If this opportunity is made, it will be very good.

alexanderkhitev avatar Feb 25 '19 22:02 alexanderkhitev

This was the only reason we had to move a lot of our apps to other platform for analytics. Anyone who has access to crashlytics will have access to in-app purchase data. We have many layers of access rights. We don't want everyone to have access to financial data, on the team.

haseebyf avatar Apr 05 '19 11:04 haseebyf

This issue is important and should be addressed.

sc0rch avatar Apr 12 '19 15:04 sc0rch

Tracked internally at b/130422135

paulb777 avatar Apr 12 '19 17:04 paulb777

Any chance get it soon?

Igor-Poltavtsev avatar May 08 '19 16:05 Igor-Poltavtsev

179 days passed, just a reminder

sc0rch avatar Sep 24 '19 05:09 sc0rch

Any update on this?

skuske avatar Oct 18 '19 11:10 skuske

I needed a team member to have access to crashlytics only and was not supposed to have access to in-app purchase and Admob data. I ended up creating a new role in IAM. It works but control of 'auto logging' would make things a lot easy.

haseebyf avatar Oct 18 '19 17:10 haseebyf

I just found this through Google:

"By default, the SDK collects in-app purchase information on iOS via the public transaction observer methods from Apple. On Android, this is enabled via Google Play In-app Billing. Both iOS and Android in-app purchase tracking can be turned off via the disableAutomatedInAppPurchaseReporting() method."

Found at the bottom of https://support.google.com/firebase/answer/6318039?hl=en

Looks like this is a GADMobileAds method, and not a Firebase method, though.

skuske avatar Oct 20 '19 10:10 skuske

I needed a team member to have access to crashlytics only and was not supposed to have access to in-app purchase and Admob data. I ended up creating a new role in IAM. It works but control of 'auto logging' would make things a lot easy.

Can you explain how you created the role in IAM?

paab72 avatar Feb 13 '20 07:02 paab72

I quickly wrote down some steps for myself to remember, at that time. I am not sure if they will be work now. I have since moved my app away from Google eco-system. Here are the steps:

Firebase: Create user with Crashlytics access only

  1. Open project in firebase
  2. Select Settings->Permissions
  3. Select Advanced Permissions
  4. Select “Roles”
  5. Search “Firebase Quality Admin”
  6. Select “Create from Role”
  7. Change title from “Custom Firebase Quality Admin” to “NEW Firebase Quality Admin”
  8. Remove the permission:
    1. firebaseanalytics.resources.googleAnalyticsEdit
    2. firebaseanalytics.resources.googleAnalyticsReadAndAnalyze
  9. Save
  10. Goto IAM
  11. Add user to the new role

haseebyf avatar Feb 13 '20 09:02 haseebyf

any chance this issue could be fixed? thanks!

zhaoze1991 avatar Apr 20 '20 23:04 zhaoze1991

I just found this through Google:

"By default, the SDK collects in-app purchase information on iOS via the public transaction observer methods from Apple. On Android, this is enabled via Google Play In-app Billing. Both iOS and Android in-app purchase tracking can be turned off via the disableAutomatedInAppPurchaseReporting() method."

Found at the bottom of https://support.google.com/firebase/answer/6318039?hl=en

Looks like this is a GADMobileAds method, and not a Firebase method, though.

Hi, Have you tried it? Did it work?

Shani-Rabi avatar May 20 '20 09:05 Shani-Rabi

We haven't GADMobileAds in project, so looks disableAutomatedInAppPurchaseReporting() won't work for Firebase.

Igor-Poltavtsev avatar Jul 16 '20 17:07 Igor-Poltavtsev

Any updates on this? We want to onboard more team members to Firebase, but we don't need all of them to see revenue data.

touchberry avatar Nov 29 '20 23:11 touchberry

bump, our analytics data is at risk of being ruined by users who 'hack' IAP's. Our backend filters out invalid attempts by validating the receipt ID"s, but the attempts are logged to Firebase Analytics anyway so now our dashboard has a random day where we made 10,000% more than we usually make.. all thanks to one rouge user. It makes the chart illegible now since everything else (our 'valid' data) by comparison is crushed to near zero..

We'd like to report in_app_purchase manually once we validate the purchase on our backend

timbo-tj avatar Mar 21 '23 22:03 timbo-tj

Any update on it?

slavasemeniuk avatar May 16 '24 06:05 slavasemeniuk

@paulb777 do you have any updates on this feature?

muneer-khan avatar May 17 '24 14:05 muneer-khan

This is not on the roadmap at this time. The use cases described above can be addressed by using features such as data-restriction management or user deletion. Closing this ticket for now, but feel free to provide more details on the underlying use cases not already described.

htcgh avatar Jun 12 '24 23:06 htcgh