Appodeal Android, java.lang.NullPointerException

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

 Hi! Looking at the crash reports from google play we’re seeing an increase in crashes from the appodeal plugin since updating with the latest version in our apps. About 1 - 1.5% of our sessions gets this null pointer crash. Would be great if this could be fixed! 

java.lang.NullPointerException :

 

at plugin.appodeal.LuaLoader.dispatchLuaEvent (LuaLoader.java:285)

 

at plugin.appodeal.LuaLoader.access$1600 (LuaLoader.java:39)

 

at plugin.appodeal.LuaLoader$AppodealInterstitialDelegate.onInterstitialFailedToLoad (LuaLoader.java:1268)

 

at com.appodeal.ads.r$2.run (Unknown Source)

 

at android.os.Handler.handleCallback (Handler.java:815)

 

at android.os.Handler.dispatchMessage (Handler.java:104)

 

at android.os.Looper.loop (Looper.java:207)

 

at android.app.ActivityThread.main (ActivityThread.java:5692)

 

at java.lang.reflect.Method.invoke (Native Method)

 

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:905)

 

at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:766)

Let me know if i should forward this to the appodeal team as well

Thanks!

#2

It probably won’t hurt to forward this to Appodeal as well. I’ll reach out to the team and see if this makes any sense.

Rob

#3

Our engineers feel these are errors coming from older builds of the Appodeal plugin and that this is a bug that has already been fixed. Have you released an update recently? Do you have stats on how many people are running older versions of your app?

Rob

#4

Thanks Rob! Great that you’re looking into this! 

These errors first appeared in the latest update we did for Hanger.  It was built using Corona 3068 on August 10, to get the latest appodeal SDK 2.0 in. Google play filters on app version so we can see it started happening with that version. 

Thanks!

#5

Okay I’ll pass this information back.

Rob

#6

That would be correct. A build around then would have used version 1.3 of the plugin. The fix was made in 1.3.2 which was released on Aug 29.  Try building and submitting a new version.

Rob

#7

Ok! Great to hear it’s fixed already, we’ll do a new release asap.

It would be great if there was a way to get notified when a new version of a plugin updates and things like this gets fixed. Would have saved us some time in this case. 

Thanks!

#8

We do try and post updates to the Monetization forum.

https://forums.coronalabs.com/forum/545-monetization-in-app-purchases-ads-etc/

I guess we may miss some from time to time but that’s the place to look.

Rob

#9

@Chribbe

You can check which version of the plugin is being used by checking your device log during testing.

Our plugins always log the plugin version in the device log upon init() of the plugin.

For this plugin you should see an entry like this in the device log:

I/Corona (12345): plugin.appodeal: 1.3.3 (SDK: 2.1.3) 

#10

I think plugin version should be tied to CoronaSDK version.

if I released an app and tested monetization thoroughly, then one month later I release and update with minor spelling fix, I don’t want a whole new set of monetization plugins to be used.

CoronaSDK should come with a set of plugins.

then in coronaSDK release notes you add a bullet about sub-tools / plugins updates

#11

Hi ingemar_cl,

I did a build this morning but the console log still shows the app is using 1.3 instead of 1.3.3

5892-5918/? I/Corona: plugin.appodeal: 1.3

I’m using Corona 2017.3135 on a Mac.

Is there something else I have to do in order to get the latest vesion of the Appodeal plugin?

#12

Yeah, I happened to see that myself about an hour ago.

It seems like we have a build server issue affecting the Appodeal plugin. It’s picking up an old version for some reason.

I’ve asked engineering to have a look.

#13

Ok! Would be great if you let us know here when it’s solved so we can release a new version.

#14

@chribbe

The build server issue has been resolved.

#15

@ingemar_cl

Thanks - doing a new build today

#16

@Chribbe

Just a heads-up.

Please double check in your device logs during testing that you get plugin version 1.3.3

Today the build servers decided to revert back to plugin version 1.3 again for some reason.

Engineering is looking into the issue.

I’ll post here again with a status update when I know more.

#17

@Chribbe

It looks like the Appodeal plugin on one of the build servers was out of sync which was causing the issue to re-appear.

It’s fixed now, so you should be getting the latest version.

#18

@Ingemar - thanks for the heads up. Checked the console of the release we made yesterday and it says,

plugin.appodeal: 1.3.3 (SDK: 2.1.3)

so looks like it got the correct version then. 

Thanks!

#19

It probably won’t hurt to forward this to Appodeal as well. I’ll reach out to the team and see if this makes any sense.

Rob

#20

Our engineers feel these are errors coming from older builds of the Appodeal plugin and that this is a bug that has already been fixed. Have you released an update recently? Do you have stats on how many people are running older versions of your app?

Rob