FB Audience Network Crashing Since Nov. 9

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

Starting on February 9, every single one of my users who was eligible to be served ads on the FB Audience Network got a crash, iOS and Android alike. I was able to fix the problem by issuing updates that didn’t call FAN, but I have no idea what caused the crashes to suddenly start happening, and why I’m seemingly the only person who’s having this problem.
I spent the better part of the last three days exclusively dealing with customer support, and I’m tempted to just shrug my shoulders and move on without FAN, but it is a lucrative ad network, and I’d like to bring it back if I can figure out what’s going on.

Here’s what I think is the relevant piece of the crash from Logcat (time stamps removed for clarity):

ERROR: Runtime error
java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Integer.intValue()' on a null object reference
Java Stack Trace:
	plugin.fbAudienceNetwork.LuaLoader$load.invoke(LuaLoader.java:858)
	com.ansca.corona.JavaToNativeShim.nativeTouchEvent(Native Method)
	com.ansca.corona.JavaToNativeShim.touchEvent(JavaToNativeShim.java:439)

Here is the plugins section of my build.settings file:

plugins =
    {
	["plugin.animation"] =
		{
		publisherId = "com.coronalabs"
		},

	["plugin.flurry.analytics"] =
		{
		publisherId = "com.coronalabs"
		},
		
	["plugin.appsflyer"] =
		{
		publisherId = "com.coronalabs",
		},

-- IAP Plugins
	["plugin.google.iap.v3"] =
		{
		publisherId = "com.coronalabs",
		supportedPlatforms = { android=true, },
		},

	["plugin.iap_badger"] =
		{
		publisherId = "uk.co.happymongoose",
		},

-- Social Plugins
	["CoronaProvider.native.popup.activity"] =
		{
		publisherId = "com.coronalabs",
		supportedPlatforms = { iphone=true, },
		},

	["CoronaProvider.native.popup.social"] =
		{
		publisherId = "com.coronalabs",
		supportedPlatforms = { android=true, },
		},

-- Advertising Plugins
	["plugin.chartboost"] =
		{
		publisherId = "com.coronalabs",
		supportedPlatforms = { iphone=true, android=true, }
		},

	["plugin.adcolony"] =
		{
		publisherId = "com.coronalabs",
		supportedPlatforms = { android=true, }
		},

	["plugin.admob"] =
		{
		publisherId = "com.coronalabs",
		supportedPlatforms = { iphone=true, android=true, }
		},

	["plugin.applovin.paid"] =
		{
		publisherId = "com.coronalabs",
		supportedPlatforms = { android=true, }
		},

	["plugin.vungle"] =
		{
		publisherId = "com.vungle",
		supportedPlatforms = { iphone=true, }
		},

	["plugin.fbAudienceNetwork"] =
		{
		publisherId = "com.coronalabs",
		supportedPlatforms = { iphone=true, android=true, }
		},
				
	["plugin.facebook.v4a"] =
		{
		publisherId = "com.coronalabs",
		supportedPlatforms = { iphone=true, }
		},
				
	["plugin.unityads"] =
		{
		publisherId = "com.coronalabs",
		supportedPlatforms = { iphone=true, android=true, }
		},

	},
}

Both the iOS and Android versions were built with Solar2D v3620 and had, up until Nov. 9th, been working fine. This crash did not come right after an update- it happened out of the blue. The only triggering factor I can think of is that Facebook has been talking about changes that they would be making in response to iOS 14, and this happened the same day that iOS 14.2 started rolling out.

Anyone have any ideas? @vlads?

#2

That is brutal. I am looking into updating FAN. Will let you know.

#3

Thank you, @vlads!

#4

android_error_FAN_plugin
android_error_FAN_plugin1080×2280 209 KB

Hi Vlad;

I have had exactly the same experience. As a result, I’ve taken all Facebook Audience Network ads out of my setup on my several apps. My theory is that Facebook changed some critical data that was being returned to the plugin after a “load” call and the plugin’s inability to deal with this data (or a nil return) is triggering this error. The exact error language can be seen in the attached screen capture.

Sure hope that this can get remedied soonest as it costs real money over time.

Thanks.

Steve

#5

I just realized I wrote “Feb. 9” instead of “November 9”. I was pretty stressed out when I wrote the post.
@sbullock- I’m sorry to hear that you got bit by the same bug.