关闭FireBase的混乱不仅会影响推送收据，还会影响分析? [英] Does turning off FireBase swizzling affect analytics besides push receipts?

问题描述

Firebase云消息传递文档说，他们在为了获得推送通知令牌并记录接收推送通知.在 FIRAnalytics文档中，某些事件名称是保留的(请参见下面的logEventName:parameters:)，包括in_app_purchase.这表明Firebase会自动将应用程序内购买记录到他们的分析中，这似乎很难自动完成.

The Firebase cloud messaging documentation says that they swizzle some methods in order to get a push notification token and log receiving a push notification. In the FIRAnalytics documentation, some event names are reserved (see under logEventName:parameters:), including in_app_purchase. This suggests that Firebase is automatically logging in-app purchases to their analytics, which seems difficult to do automatically without swizzling.

Firebase是否会为了使用这些保留的关键字而混乱?如果是这样，是否可以通过FirebaseAppDelegateProxyEnabled关闭混浊功能来禁用这些分析?

Does Firebase swizzle in order to use these reserved keywords? If so, does turning off swizzling via FirebaseAppDelegateProxyEnabled disable these analytics?

推荐答案

否，将FirebaseAppDelegateProxyEnabled设置为NO将仅禁用App Delegate方法的混乱.由于Google Analytics(分析)不会从您的应用程序委托中获取应用程序购买事件，因此它不会影响应用程序购买事件.如文档所述，唯一会影响Google Analytics(分析)的是广告系列通过使用URL/通用链接打开应用来进行事件.如果您决定在仍要支持广告系列事件的同时将其关闭，则建议添加文档中所述的方法.

No, setting FirebaseAppDelegateProxyEnabled to NO will disable the swizzling of the App Delegate methods only. It will not affect in app purchase events since Analytics does not get in app purchase events from your App Delegate. As mentioned in the documentation, the only thing that will affect Analytics is campaign events through opening app with URLs/Universal Links. If you decide to turn it off while you still want support for campaign events, it is recommended to add the methods as described in the documentation.

这篇关于关闭FireBase的混乱不仅会影响推送收据，还会影响分析?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！