Facebook v4a plugin - console warnings

Solar2D Monetization (in-app purchases, ads, etc.)
#1

I’m trying to use the Facebook v4a plugin to track app installs. It seems to be working fine, and the call to init() succeeds. I can also see an app install being recorded on my Facebook app’s dashboard.

But in the console I get the following warnings:

<Warning>: Please set a value for FacebookAutoLogAppEventsEnabled. Set the flag to TRUE if you want to collect app install, app launch and in-app purchase events automatically. To request user consent before collecting data, set the flag value to FALSE, then change to TRUE once user consent is received. Learn more: https://developers.facebook.com/docs/app-events/getting-started-app-events-ios#disable-auto-events.
<Warning>: You haven't set a value for FacebookAdvertiserIDCollectionEnabled. Set the flag to TRUE if you want to collect Advertiser ID for better advertising and analytics results.

Does the plugin have support for these settings that the Facebook SDK is complaining about? I can’t seem to find any information about this in the docs or forums.

#2

i don’t believe it does. I think Scott H had a plugin for Facebook that might be more up to date.

#3

I can’t find any at https://solar2dmarketplace.com/, only the Facebook Analytics plugin.

Anyway, from what I understand when reading at Facebook’s docs they (the settings I’m getting warnings about) are enabled by default which is exactly what I want. https://developers.facebook.com/docs/app-events/getting-started-app-events-ios#disable-auto-events

So hopefully that means I can use it for now, until the bigger iOS 14 changes comes into play…

#4

Hi @Markus_Ranner
any update on this?
I want to set FacebookAdvertiserIDCollectionEnabled to true, only after get user consent.

I am building with solar2d native/enterprise, and would add native API to the facebook-v4a but there is no source code in the v4a plugin!

I guess, also adding facebook SDK will conflict with v4a plugin…
so is there any workaround for this?

Thanks…

#5

Nothing new that I know of. What I’ve done is to just wait to get user consent before I try to initialize the v4a plugin.