corona beacon error - Build: 2018.3215

Solar2D General Questions/Discussion
#1

On Android, I have noticed this error lately. I don’t know if it has been resolved on one of the newest builds but I am using Build: 2018.3215.  Also does not appear to be limited to a particular  OS.

  • lang.java.NullPointerException: (Attempt to invoke virtual method ‘void com.ansca.corona.CoronaRuntimeTaskDispatcher.send(com.ansca.corona.CoronaRuntimeTask)’ on a null object reference)

at corona.ansca.com.CoronaBeacon$2.run(CoronaBeacon.java:116)

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

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

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

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

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

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

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

 

#2

What plugins are you using?

Rob

#3

If CoronaBeacon doesn’t ring a bell and you might think it is a plugin then don’t worry I’ll figure it out. I have to see what the build file looked like in the last few releases, but I don’t believe I have anything unusual: Appodeal, Gamesparks & Flurry. I’ll report back if I deduce anything.

#4

We use beacons in our ad plugins (and maybe others) to report back to us when ads are shown, what type etc. so we can provide reporting back to the ad vendors.  So that rings a bell. This is why I asked what plugins you are using. Of the plugins you mentioned, Appodeal would certainly be a leading candidate for us to look into.

Are you using the original Appodeal plugin or the new modular one?

Rob

#5

Yes, the new Appodeal plugin. Inter, banner and Rewarded Video. The Inter will only show static if the user is connected to a mobile network (if that helps at all). I am going to switch over to AdMob for a few days to see if the error goes away. Thank you for the help Rob.

#6

Hi agramonte,

From the couple lines of log that you have provided, it looks like the problem is not in the CoronaBeacon itself, but in the data, that it’s sending, it may be corrupted somehow. Then again, it’s not something that you have control over.

To help you with that we need some kind of a way to reproduce it. For now, I haven’t seen that issue on any of our test samples. I’ll try to check some parameters combination for Appodeal, but, as always, it would be much faster if you can give us a sample at https://portal.coronalabs.com/bug-submission

#7

No chance I can replicate it. It wouldn’t even be an issue if it wasn’t for the crappy threshold waste of time that Google has us going through.

It happens very infrequently, but frequently enough to add significantly to the allowed crash threshold. Here is some more info:

It says it is occurring on CoronaBeacon.java line 116.

It is impacting 0.6% of my users (not sessions but users).

Is it possible the next time this file gets updated to add a null check on whatever object is being invoked? Just a thought. Anway thank you for all the help. Always appreciate it.

#8

It’s sad that we can’t reproduce an issue straight away. I’ll investigate more and write some kind of a report in this thread when I’ll have some info.

Thank you for your help and I mean it. Some bugs are seeping to production (which we are aiming to eliminate in the nearest future, impoving qa department and stuff, a lot of work is going on) and we’ve got a lot of feedback specifically from you, agramonte, and it’s really helpful.

Sure thing, the bugs shouldn’t appear in the first place, but having this kind of supporting community is really neat. I hope that soon most of that feedback will be about improving things and not fixing them, all our team is working hard to raise the level of product quality.  B)

#9

 @karpovpw

When all the bugs are worked out it will be great… I have loads from 6+ months ago yet to be dealt with.  Like live builds do not respect landscape only apps.

You won’t find it in the support log as it “was deleted” months ago.  

Doesn’t mean it is still not a bug!

So sad that bug reports “go missing” if they are too tricky to fix.

#10

I’ll try to get some info about this bug and whole bug reports missing thing.

#11

Removed appodeal and no errors in 3 days. Now I am going to add appodeal back with most of the plugins. Let you know how it goes.

#12

Thanks for the feedback, any info is welcomed.

No news from me for now, sadly. CoronaBeacon code is fine, it’s quite simple to be honest and it’s being accessed, like, thousands and thousands times a day with no issues whatsoever. It may be some threading issue, caused by something, but may be not. Still can’t reproduce it with any ad plugin I’ve tried. But we are working on it, I know that it’s not sounds that promising, but it will be fixed asap, no worries!

#13

Some update: while we are looking on a problem reproduction, we’ve changed CoronaBeacon reaction to input parameters. Now there wont be a crash, but an error in log. Update should be public soon.

Still no news on the source of an issue though, it’s really getting on my nerves.

#14

First I want to say I think Appodeal does a great job. I have been using Appodeal on and off before I ever started using Corona (MadeWithMarmalade). Defects will always show up and it is a part of life when you are developing software. I currently have 12 defects under my name in my other job all due for the next build (tomorrow).

My latest update. Keep in mind that my goal was to get it stable and not to figure out where the problem was.

The error has completely disappeared (I was getting a few a day and I have gotten 0 in the last few days). I am up to this version of Corona: 2018.3228

I am left with only these “appodeal plugins”.

--Base ['plugin.appodeal.base'] = { publisherId = 'com.coronalabs' }, ['plugin.appodeal.AmazonAds'] = { publisherId = 'com.coronalabs' }, ['plugin.appodeal.TwitterMoPub'] = { publisherId = 'com.coronalabs' }, ['plugin.appodeal.StartApp'] = { publisherId = 'com.coronalabs' }, ['plugin.appodeal.GoogleAdMob'] = { publisherId = 'com.coronalabs' }, -- End of Base ['plugin.appodeal.AppLovin'] = { publisherId = 'com.coronalabs' }, ['plugin.appodeal.MillenialMedia'] = { publisherId = 'com.coronalabs' } ['plugin.appodeal.Chartboost'] = { publisherId = 'com.coronalabs' },
#15

@karpovpw with regard to support tickets going missing here is one…

ticket was # 12934639

#16

The ticket certainly exists. The software we use does not have a customer facing view. You can’t just hit the URL and see the ticket. Email is the primary means of communications, so as long as your email is correct, you should be getting replies.

There have been two internal comments added, one to add Vlad to the ticket and one adding the URL from your Forum thread: https://forums.coronalabs.com/topic/71862-signal-11-sigsegv-code-1-segv-maperr-art-quick-imt-conflict-trampoline/#entry376358

I’ll see if I can find out where we are at looking at it.

Rob

#17

@rob I am simply clicking on the view link in the response - maybe the issue is with your software then?

Yes, my email is correct and I have zero replies.

#18

Lets continue the conversation on the ticket so we don’t misdirect this forum topic and it’s only being answered in one place.

Thanks

Rob

#19

It seems that there can be some kind of race conditions, but that’s not some plugin specific issue or something. Our latest changes fixed android crashes completely, but thanks to this thread and a feedback we are looking more closely at threads safety now for you.

Glad that everything works out specifically, agramonte, as always - feel free to share any more issues and concerns, we’ll gladly help to figure them out!

#20

What plugins are you using?

Rob