NullPointerException in MobileAds.initialize

[Albert Gazetdinov]

use com.google.android.gms:play-services-ads-lite:18.1.1

see many bugs:

java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.endsWith(java.lang.String)' on a null object reference
    at com.google.android.gms.internal.ads.zzwv.zzpe (SourceFile:27)
zza
    at com.google.android.gms.ads.MobileAds.initialize (SourceFile:3)
initialize

[Albert Gazetdinov]

i use 

    <meta-data
        android:name="com.google.android.gms.ads.DELAY_APP_MEASUREMENT_INIT"
        android:value="true"/>

среда, 21 августа 2019 г., 9:38:24 UTC+3 пользователь Albert Gazetdinov написал:

[Albert Gazetdinov]

com.google.android.gms.internal.ads.zzwv.class

private final boolean zzpe() throws RemoteException {
    try {
        return this.zzcen.getVersionString().endsWith("0");
    } catch (RemoteException var1) {
        zzawo.zzes("Unable to get version string.");
        return true;
    }
}

this.zzcen.getVersionString() sometimes return NULL

please fixed in next version

среда, 21 августа 2019 г., 9:38:24 UTC+3 пользователь Albert Gazetdinov написал:

use com.google.android.gms:play-services-ads-lite:18.1.1

[Mobile Ads SDK Forum Advisor Prod]

Hello there,

Thanks for reaching out to us. Are you able to reproduce the issue with our sample apps? Can you please share the complete device logs and a sample project for us to take a look and debug this issue further? You can use "Reply Privately to Author" option to share the details privately. 

Regards,
Deepika Uragayala
Mobile Ads SDK Team
 

ref:_00D1U1174p._5001UHEBuR:ref

[林坚洪]

same issue when upgrade to 18.1.1 version. ( Honor 5c  6.0 ), however, it work well on vivo z1 9.0

this happen on call MobileAds.initialize(context, ADMOB_APP_KEY)

this is the crash info, 

Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.endsWith(java.lang.String)' on a null object reference

        at com.google.android.gms.internal.ads.zzwv.zzpe(com.google.android.gms:play-services-ads-lite@@18.1.1:138)

        at com.google.android.gms.internal.ads.zzwv.zza(com.google.android.gms:play-services-ads-lite@@18.1.1:40)

        at com.google.android.gms.ads.MobileAds.initialize(com.google.android.gms:play-services-ads-lite@@18.1.1:7)

        at com.google.android.gms.ads.MobileAds.initialize(com.google.android.gms:play-services-ads-lite@@18.1.1:3)

        at com.mix.ad.AdManagerHelper.initAd(AdManagerHelper.java:221)

        at com.mix.ad.AdManagerHelper.<init>(AdManagerHelper.java:92)

        at com.mix.ad.AdManagerHelper.getInstance(AdManagerHelper.java:111)

        at com.xmode.launcher.LauncherApplication.onCreate(LauncherApplication.java:266)

        at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1015)

在 2019年8月22日星期四 UTC+8上午3:55:58，mobileadssdkforumadvisor写道：

[Mobile Ads SDK Forum Advisor Prod]

Hello there,

Are you able to reproduce the issue locally? Is this crash specific to any devices as you mentioned? Can you please provide us any additional details like crashlytics/additional crash logs to help us in debugging this further?

[Ann]

Hi there, any updates on this matter?

We have just updated Ironsource to latest version(6.9.1.1) and Admob (18.2.0) to the latest version and is now seeing this crash.

Does it help to bump up play-services-ads-lite to version 18.2.0 instead of 18.1.x?

Thanks

/Ann

[Mobile Ads SDK Forum Advisor Prod]

Hello there,

We are not able to reproduce any crashes with the latest version of the regular SDK. Is this happening only with the lite version of the SDK? Also, it would be really helpful if you could share complete crash logs and any steps to reproduce the issue on our end.

[James Daniels]

I am also getting this using ads-lite 18.3.0 (haven't tested the non-lite version). Note that this only occurs on some devices (e.g. the Nokia 1 as used in the pre-launch report). As Albert mentioned earlier in the thread, this is probably due to getVersionString returning null on some devices. Seems like it should be a simple bug to fix, and quite urgent?

Here's a sample crash log:

FATAL EXCEPTION: main
Process: net.apex_designs.payback2, PID: 10433
java.lang.RuntimeException: Unable to start activity ComponentInfo{net.apex_designs.payback2/net.apex_designs.payback2.MyNativeActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.endsWith(java.lang.String)' on a null object reference
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2805)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2883)
	at android.app.ActivityThread.-wrap11(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1613)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:6523)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:857)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.endsWith(java.lang.String)' on a null object reference
	at com.google.android.gms.internal.ads.zzxq.zzpx(com.google.android.gms:play-services-ads-lite@@18.3.0:136)
	at com.google.android.gms.internal.ads.zzxq.zza(com.google.android.gms:play-services-ads-lite@@18.3.0:38)
	at com.google.android.gms.ads.MobileAds.initialize(com.google.android.gms:play-services-ads-lite@@18.3.0:7)
	at com.google.android.gms.ads.MobileAds.initialize(com.google.android.gms:play-services-ads-lite@@18.3.0:3)
	at net.apex_designs.payback2.MyNativeActivity.onCreate(MyNativeActivity.java:1299)
	at android.app.Activity.performCreate(Activity.java:7013)
	at android.app.Activity.performCreate(Activity.java:7004)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1214)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2758)
	... 9 more

Thanks,

James.

[James Daniels]

BTW, rolling back to ads-lite 18.0.0 fixes the issue.

[Mobile Ads SDK Forum Advisor Prod]

Hello James,

Thanks for sharing the details and the crash logs. I have shared this issue with the rest of the team for further investigation. We will keep you posted if we have any update from our team.

[Julian Eggers]

Is there any progress in fixing this issue?

[Mobile Ads SDK Forum Advisor Prod]

Hi Julian,

 

Thank you for reaching out to us.

 

If this issue is still occurring on your end, could you then kindly provide the details below (via Reply privately to author) in order to help with the investigation?

• AdMob SDK version
• Device name and Android version
• Copy of a sample project (replicating the issue)
• Steps to replicate the issue

 

Regards,

Ziv Yves Sanchez

Mobile Ads SDK Team

ref:_00D1U1174p._5001UOFJD6:ref

[Mohammad Forhad Talukder]

[Tomáš Kuba]

Hi, the problem occurs also on my app. 67 of such events today in Crashlytics (3-fold increase in the last days). Using ads-lite:18.3.0. A lot of devices: Huawei, Samsung, Sony, Allwiner, Lenovo, Amlogic, ...

Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.endsWith(java.lang.String)' on a null object reference
       at com.google.android.gms.internal.ads.zzxq.zzpx(zzxq.java:136)

[James Daniels]

This should be a high priority issue to fix as soon it will be required to use the latest ads-lite (due to the play referrer api changes coming into effect on 1 march) so the workaround of using an older version will no longer be possible.

Please fix this soon!

Thanks,
James.

[Marek Potkan]

Same bug in our apps. Everything worked perfectly with play-services-ads library. However, recently we migrated to play-services-ads-lite version 18.3.0 and the bug appeared (different devices and OS versions). Now we need to use downgraded version 18.0.0 as the bug is not present there. Could this be fixed ASAP? As James Daniels wrote, we will need to use the latest version soon due to the play referrer API changes.

Dňa piatok, 27. decembra 2019 8:20:42 UTC+1 mobileadssdkforumadvisor napísal(a):

[Mobile Ads SDK Forum Advisor Prod]

Hi all,

Hope this post finds you well.

I've made a follow up to the team regarding the issue. I'll update this thread the soonest they provide their feedback.

Regards,
Teejay Pimentel

[James Daniels]

Any news? We're going to have to drop ads-lite if this isn't fixed very soon :/

Thanks,

James.

[Mobile Ads SDK Forum Advisor Prod]

Hi all,

Thank you for your patience. Please be informed that the team is currently on the testing and evaluation phase for the aforementioned fix. I'll update this thread as soon as the fix has been released.

[Mobile Ads SDK Forum Advisor Prod]

Hi all,

Please be informed that the fix will be available to the next SDK release. Kindly keep an eye on our release notes regarding this.

[Twinkle Dating App]

Just curious what is the connection between using the newer ads-lite and the deprecation of the install referrer broadcast? I do not see any connection in the recent release notes here: https://developers.google.com/admob/android/rel-notes. What will break exactly? I can only assume some implication about Admob using the broadcast receiver to track installs of apps it's shown ads for in my app, but... hasn't the install referrer replacement library been around for ages?

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for reaching out to us. However, I'm afraid we're having trouble understanding your inquiry. The install referrer broadcast is an intent broadcast when an app is installed from the Google Play Store which cannot be compared to the Mobile Ads SDK lite. Could you elaborate the details of your concern so we could provide our insight precisely?

Regards,
Teejay Pimentel
Mobile Ads SDK Team

ref:_00D1U1174p._5001UXTWg9:ref

[James Daniels]

The latest public version of ads-lite (18.3.0) has a bug that makes it crash on some devices (the null pointer exception referenced in this thread). Using an older version (18.0.0) fixes that problem, but old versions still rely on the install referrer broadcast, so that workaround is no longer usable after 1 March. A new version with a fix for the null pointer exception issue is in the works apparently but has not yet been released.

I believe the install referrer broadcast is used to match up the ad click with the app install (both your app and the app that gets installed due to the advert would call it). I'm expecting the deprecation to mean that at some point after 1 March installs won't be tracked properly, which I would expect to lower eCPMs. It's also possible it might cause crashes or other problems. I don't work for Google though so I can't say for sure. I'm hoping they release the fixed version soon.

Thanks,

James.

[Mobile Ads SDK Forum Advisor Prod]

Hello James,

Thanks for chiming in. As of now, we haven't heard of any such issues. If we receive any concerns regarding this, we will be happy to take a look.

Regards,
Deepika Uragayala

[Mobile Ads SDK Forum Advisor Prod]

Hi all,

Please be informed that the fix has been released. Kindly let us know if you still encounter the issue using the latest version of the SDK, so I could raise this to the team once more.

Regards,
Teejay Pimentel

Mobile Ads SDK Team

ref:_00D1U1174p._5001UOFJD6:ref

[Tomáš Kuba]

Hi,

we have updated the ads lite lib to 19.0.0, however it still crashes:

Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.endsWith(java.lang.String)' on a null object reference

       at com.google.android.gms.internal.ads.zzxu.zzpz(zzxu.java:136)

       at com.google.android.gms.internal.ads.zzxu.zza(zzxu.java:38)

       at com.google.android.gms.ads.MobileAds.initialize(MobileAds.java:7)

       at com.google.android.gms.ads.MobileAds.initialize(MobileAds.java:3)

       ...

First occurence on HUAWEI Y6 2018. 

Should you require more information, please tell us, we can provide further data.

Thank you in advance for the prompt fix.

[James Daniels]

Yes, we've just tested it too and we get the same problem. Only on some devices (e.g. Nokia 1) and possibly only when downloaded from the play store (or via the pre-launch report).

James.

[James Daniels]

Note the Nokia 1 runs the Go edition of Android 8.1. This might be related to the cause of the crash - perhaps there are APIs missing in the Go edition?

James.

[Mobile Ads SDK Forum Advisor Prod]

Hi all,

Thank you for getting back to us. Let me raise this information back to the team. I'll update this thread the soonest they provide their feedback.

[Twinkle Dating App]

I'd just like to mention that I get the same exception, with a different stack trace - MobileAds.initialize not even on the stack. In case this helps. This was found via prelaunch report on Nokia 1.

java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.endsWith(java.lang.String)' on a null object reference
	at com.google.android.gms.internal.ads.Re.c(SF:1)
	at com.google.android.gms.internal.ads.Re.a(SF:23)
	at com.google.android.gms.ads.k.a(SF:3)
	at com.google.android.gms.ads.k.a(SF:1)
	at letstwinkle.com.twinkle.wa.a(SF:20)
	at letstwinkle.com.twinkle.wa.a(SF:1)
	at letstwinkle.com.twinkle.api.v.b(SF:1)
	at letstwinkle.com.twinkle.api.I.b(SF:5)
	at letstwinkle.com.twinkle.api.I.a(SF:2)
	at letstwinkle.com.twinkle.api.D.a(SF:5)
	at letstwinkle.com.twinkle.api.G.a(SF:9)
	at letstwinkle.com.twinkle.api.G.a(SF:1)
	at com.android.volley.f$a.run(SF:4)
	at android.os.Handler.handleCallback(Handler.java:790)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:6523)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:857)

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for you additional context. Let me raise this to the team as well. I'll update this thread the soonest they provide their feedback.

[Twinkle Dating App]

I said this:

> I'd just like to mention that I get the same exception, with a different stack trace

Actually, I should probably have thought a bit more. My crash report clearly did not deobfuscate the symbols. It was from the Pre-launch testing feature.

The traces from the OP, I'm sure they applied deobfuscation from the Play Store or Crashlytics etc.

My stack trace could be the same after all. Sorry for the confusion!

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for your additional insight. Please be informed that this has been raised to the team for further investigation. I'll update this thread the soonest we have our findings.

[Máté Lebedy]

I've got the same problem, Nokia 1 (Android 8.1 Go edition) pre-launch report displays a crash with the following stacktrace:

Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.endsWith(java.lang.String)' on a null object reference
 at com.google.android.gms.internal.ads.zzxu.zzpz(com.google.android.gms:play-services-ads-lite@@19.0.0:136)
 at com.google.android.gms.internal.ads.zzxu.zza(com.google.android.gms:play-services-ads-lite@@19.0.0:38)
 at com.google.android.gms.ads.MobileAds.initialize(com.google.android.gms:play-services-ads-lite@@19.0.0:7)
 at com.google.android.gms.ads.MobileAds.initialize(com.google.android.gms:play-services-ads-lite@@19.0.0:9)

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

 

Thank you for reporting this and for providing the additional stacktrace. Allow me to also raise this with the rest of the team for further investigation.

 

We'll keep you posted for any updates available via this thread.

 

Regards,

Mark Albios

Mobile Ads SDK Team

ref:_00D1U1174p._5001UXVbfj:ref

[Máté Lebedy]

Hi!

Tested again with 19.0.1 and the problem disappeared, no crash in pre-launch report.

Thanks!

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

 

Thank you for confirming that the issue is no longer existing when using the 19.0.1 SDK version.

[Mobile Ads SDK Forum Advisor Prod]

Hi all,

We have received a report from other publishers that the issue is no longer exists on the latest version of the SDK. With this, could you kindly update to the latest version of the SDK and let us know if you still encounter the crash?

Regards,
Teejay Pimentel

Mobile Ads SDK Team

ref:_00D1U1174p._5001UOFJD6:ref

[Máté Lebedy]

Sorry, the pre-launch report was misleading, because it reported 0 errors but the automatic test for the Nokia 1 was not executed properly.

(the app could not be started but no stacktrace was produced).

I ran the pre-launch report again and the problem still persists.

Sorry for my misleading message.

Looking forward for the bugfix. Thanks.

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

 

Thank you for getting back to us that the fix was a mistake. I will be sharing that with the rest of my team.

 

Regards,

Aryeh Baker

Mobile Ads SDK Team

ref:_00D1U1174p._5001UXVbfj:ref

[Mobile Ads SDK Forum Advisor Prod]

Hi Máté,

 

Thank you for your patience on this matter.

 

The fix should be available in our next AdMob SDK release after 19.0.1. However, I'm afraid that we are unable to provide a specific ETA nor timeline for such releases. You may follow our blog or release notes for future updates on this matter.

 

Regards,

Ziv Yves Sanchez

[Abu Nayem]

By using play-services-ads-lite:19.0.1 getting this error in the pre-launch report

[Mobile Ads SDK Forum Advisor Prod]

Hi Abu,

Thank you for bringing this issue to our attention.

Based on the release notes here, this issue should be fixed with 19.1.0.

If possible can you send a Charles log, or a more detailed logcat. So that we can look it over or try to see what the exact error is.

I also saw that it was working ok a few weeks back?

Regards
William Pescherine

[Tomáš Kuba]

Hi, it seems that this issue has been fixed. Thank you very much.

[pornpoj juljaroendun]

วิธีดูและเพิ่มรายได้ต้องทำอย่างไรอ่ะครับ

ในวันที่ อ. 12 พ.ค. 2020 00:09 Tomáš Kuba <tomas....@gmail.com> เขียนว่า:

Hi, it seems that this issue is fixed. Thank you very much.

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/1fb80ee5-7744-47a6-97e9-910e24e15e54%40googlegroups.com.

[Алексей Межевикин]

Hi guys. I have the same problem. I use com.google.android.gms:play-services-ads-lite:19.3.0

 

Samsung Galaxy A10s (a10s), 1792MB RAM, Android 10

Сообщить о проблеме 1 из 2

java.lang.RuntimeException:

 at android.app.ActivityThread.handleMakeApplication (ActivityThread.java:7044)

 at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6989)

 at android.app.ActivityThread.access$1500 (ActivityThread.java:272)

 at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2055)

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

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

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

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

 at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)

 at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1100)
Caused by: java.lang.RuntimeException:

 at android.app.LoadedApk.createOrUpdateClassLoaderLocked (LoadedApk.java:787)

 at android.app.LoadedApk.getClassLoader (LoadedApk.java:991)

 at android.app.ContextImpl.getClassLoader (ContextImpl.java:390)

 at com.google.android.gms.dynamic.RemoteCreator.a (RemoteCreator.java:13)

 at com.google.android.gms.internal.ads.zzzd.zzi (zzzd.java:2)

 at com.google.android.gms.internal.ads.zzwb.zzpo (zzwb.java:2)

 at com.google.android.gms.internal.ads.zzwf.zzqb (zzwf.java:8)

 at com.google.android.gms.internal.ads.zzwf.zzd (zzwf.java:8)

 at com.google.android.gms.internal.ads.zzyv.zzg (zzyv.java:2)

 at com.google.android.gms.internal.ads.zzyv.zza (zzyv.java:8)

 at com.google.android.gms.ads.MobileAds.initialize (MobileAds.java:6)

 at com.google.android.gms.ads.MobileAds.initialize (MobileAds.java:6)

 at com.mezhevikin.converter.App.addAd (App.java:6)

 at com.mezhevikin.converter.App.onCreate (App.java:6)

 at android.app.Instrumentation.callApplicationOnCreate (Instrumentation.java:1190)

 at android.app.ActivityThread.handleMakeApplication (ActivityThread.java:7039)

 at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6989)

 at android.app.ActivityThread.access$1500 (ActivityThread.java:272)

 at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2055)

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

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

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

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

 at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)


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

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for raising this to us.

Allow me to raise this with the rest of the team for further investigation. We'll get back to this thread for any updates available.

Regards,
Mark Albios
Mobile Ads SDK Team

ref:_00D1U1174p._5004Q23Iopq:ref

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for your patience on this.

I've received an update from our team and would like to confirm the following details below:

• With regard to the logs that you've shared, does it cause your application to crash, or are those just error logs that the SDK catches?
• Since you're using the Lite SDK, does the device you're using have a Google play services version older than 19.3.0?

As an aside, could you try the full SDK (com.google.android.gms:play-services-ads:19.3.0) instead and confirm if the issue still exists?

Regards,
Mark Albios
Mobile Ads SDK Team

ref:_00D1U1174p._5004Q23Iopq:ref