NPE MobFoxWebView

[andypoptacular]

I've recently integrated the Mobfox SDK into our app and are using the MoPub adaptor to show banners. The following crashes seems to be occurring, do you have any ideas about what could be causing it?

Fatal Exception: java.lang.NullPointerException: Attempt to invoke interface method 'void com.mobfox.sdk.webview.MobFoxWebView$Listener.onAdResponse(com.mobfox.sdk.webview.MobFoxWebView, org.json.JSONObject)' on a null object reference
at com.mobfox.sdk.webview.MobFoxWebView$7$1.run(MobFoxWebView.java:191)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:6934)
at java.lang.reflect.Method.invoke(Method.java)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1404)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1199)

Fatal Exception: java.lang.NullPointerException: Attempt to invoke interface method 'void com.mobfox.sdk.webview.MobFoxWebView$Listener.onError(com.mobfox.sdk.webview.MobFoxWebView, java.lang.Exception)' on a null object reference
at com.mobfox.sdk.webview.MobFoxWebView$7$3.run(MobFoxWebView.java:217)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:158)
at android.app.ActivityThread.main(ActivityThread.java:7229)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)

Fatal Exception: java.lang.NullPointerException: Attempt to invoke interface method 'void com.mobfox.sdk.webview.MobFoxWebView$Listener.onNoAd(com.mobfox.sdk.webview.MobFoxWebView)' on a null object reference
at com.mobfox.sdk.webview.MobFoxWebView$7$2.run(MobFoxWebView.java:206)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:5938)
at java.lang.reflect.Method.invoke(Method.java)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1400)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1195)

[nabriski]

Hi,

I just uploaded a version with a workaround.
We are still trying to reproduce this situation but the fix should return a standard timeout for this scenario.
We have two more reports of this happening sporadically, can you reproduce it consistently?

Thanks

[andypoptacular]

Hi,

I'm still getting many crash reports with the same error. Sorry, I haven't seen it myself so I don't know what triggers it. From the look of the app logs a new activity is loaded and the crash occurs shortly after (assumably when the Mobfox banner load is attempted). Did your fix work for other people? Could the offending code be wrapped in a 'try catch' so at least it doesn't crash the app?

Thanks.

[nabriski]

Hi, Yes, this was just reported by another publisher. We are uploading a version with a better fix + try-catch in the next few hours.

On Thu, Feb 2, 2017, at 12:08 PM, andypoptacular wrote: Hi, I'm still getting many crash reports with the same error. Sorry, I haven't seen it myself so I don't know what triggers it. From the look of the app logs a new activity is loaded and the crash occurs shortly after (assumably when the Mobfox banner load is attempted). Did your fix work for other people? Could the offending code be wrapped in a 'try catch' so at least it doesn't crash the app? Thanks. — You are receiving this because you commented. Reply to this email directly, view it on GitHub[1], or mute the thread[2].

Links: 1. #52 (comment) 2. https://github.com/notifications/unsubscribe-auth/AAVH-HyPbmfAz8kLo6Nc-95SYa-qlc0zks5rYasqgaJpZM4LvkyV

[nabriski]

Hi,

You mentioned an activity, is this a problem with interstitials?

Thanks

[andypoptacular]

Hi, No, we are currently only using Mobfox banners. The Mopub adview to contain the banners is in each activity so has to unload/load a banner when the activity changes. Thanks.

…

On 2 February 2017 at 10:28, Itamar Nabriski ***@***.***> wrote: Hi, You mentioned an activity, is this a problem with interstitials? Thanks — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#52 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASrwik30LXl-cw3TXuV9GSiYH3qdQHj-ks5rYa_lgaJpZM4LvkyV> .

-- Andy Howell CTO, Poptacular Ltd Check out our hit game, 100 PICS! <https://itunes.apple.com/gb/app/100-pics-biggest-guess-picture/id652945710?mt=8> Link to Apple App Store <https://itunes.apple.com/gb/app/100-pics-quiz/id652945710?mt=8> Link to Google Play <https://play.google.com/store/apps/details?id=com.onehundredpics.onehundredpicsquiz&referrer=utm_source%3DAndroidPIT%26utm_medium%3Dcpc%26utm_campaign%3DADXADREFweb253280fa67b8a2%26utm_content%3DAD-X>

[nabriski]

Then we've just released 3.2.0 with a fix + try-catch. We will still explore this scenario to get to the root of this.

On Thu, Feb 2, 2017, at 12:33 PM, andypoptacular wrote: Hi, No, we are currently only using Mobfox banners. The Mopub adview to contain the banners is in each activity so has to unload/load a banner when the activity changes. Thanks. On 2 February 2017 at 10:28, Itamar Nabriski ***@***.***> wrote: > Hi, > > You mentioned an activity, is this a problem with interstitials? > > Thanks > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#52 (comment)> > , > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ASrwik30LXl-cw3TXuV9GSiYH3qdQHj-ks5rYa_lgaJpZM4LvkyV> > . > -- Andy Howell CTO, Poptacular Ltd Check out our hit game, 100 PICS! <https://itunes.apple.com/gb/app/100-pics-biggest-guess-picture/id652945710?mt=8> Link to Apple App Store <https://itunes.apple.com/gb/app/100-pics-quiz/id652945710?mt=8> Link to Google Play <https://play.google.com/store/apps/details?id=com.onehundredpics.onehundredpicsquiz&referrer=utm_source%3DAndroidPIT%26utm_medium%3Dcpc%26utm_campaign%3DADXADREFweb253280fa67b8a2%26utm_content%3DAD-X> — You are receiving this because you commented. Reply to this email directly, view it on GitHub[1], or mute the thread[2].

Links: 1. #52 (comment) 2. https://github.com/notifications/unsubscribe-auth/AAVH-Fmllx3sAiddxAByeH4g7M9RkzFRks5rYbECgaJpZM4LvkyV

[nabriski]

Ok, we understand the problem now. It appears the fix released is sufficient but we are now working in producing a unit test for this scenario to fully verify this.

[andypoptacular]

Hi, Thanks for the update, how long do you think it will be before you verify? If it's a short time I'll hold off releasing an update with the fix. Thanks.

…

On 2 February 2017 at 16:20, Itamar Nabriski ***@***.***> wrote: Ok, we understand the problem now. It appears the fix released is sufficient but we are now working in producing a unit test for this scenario to fully verify this. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#52 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASrwio1n8YwpYAG_VIWFgudD5qBcp5I3ks5rYgJrgaJpZM4LvkyV> .

-- Andy Howell CTO, Poptacular Ltd Check out our hit game, 100 PICS! <https://itunes.apple.com/gb/app/100-pics-biggest-guess-picture/id652945710?mt=8> Link to Apple App Store <https://itunes.apple.com/gb/app/100-pics-quiz/id652945710?mt=8> Link to Google Play <https://play.google.com/store/apps/details?id=com.onehundredpics.onehundredpicsquiz&referrer=utm_source%3DAndroidPIT%26utm_medium%3Dcpc%26utm_campaign%3DADXADREFweb253280fa67b8a2%26utm_content%3DAD-X>

[nabriski]

We will have it verified by Sunday.

On Thu, Feb 2, 2017, at 06:24 PM, andypoptacular wrote: Hi, Thanks for the update, how long do you think it will be before you verify? If it's a short time I'll hold off releasing an update with the fix. Thanks. On 2 February 2017 at 16:20, Itamar Nabriski ***@***.***> wrote: > Ok, we understand the problem now. It appears the fix released is > sufficient but we are now working in producing a unit test for this > scenario to fully verify this. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#52 (comment)> > , > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ASrwio1n8YwpYAG_VIWFgudD5qBcp5I3ks5rYgJrgaJpZM4LvkyV> > . > -- Andy Howell CTO, Poptacular Ltd Check out our hit game, 100 PICS! <https://itunes.apple.com/gb/app/100-pics-biggest-guess-picture/id652945710?mt=8> Link to Apple App Store <https://itunes.apple.com/gb/app/100-pics-quiz/id652945710?mt=8> Link to Google Play <https://play.google.com/store/apps/details?id=com.onehundredpics.onehundredpicsquiz&referrer=utm_source%3DAndroidPIT%26utm_medium%3Dcpc%26utm_campaign%3DADXADREFweb253280fa67b8a2%26utm_content%3DAD-X> — You are receiving this because you commented. Reply to this email directly, view it on GitHub[1], or mute the thread[2].

Links: 1. #52 (comment) 2. https://github.com/notifications/unsubscribe-auth/AAVH-D64N5pgiyosaOjWJ3VpBSsd08Cyks5rYgNDgaJpZM4LvkyV

[nabriski]

Hi,
In order to verify this 100% we are refactoring our code to be more testable in this aspect.
I would suggest to go live with the present version as this refactoring is something we need to test as well and it does not differ functionally from the present version.