从6月25日正在使用的广告两个不相关的应用程序开始有这个NPE

From the 25th of june two unrelated apps that are using ads started to have this NPE

java.lang.NullPointerException
   at zo.a(SourceFile:172)
   at aeh.a(SourceFile:120)
   at afw.run(SourceFile:14)
   at afy.run(SourceFile:30)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
   at java.lang.Thread.run(Thread.java:856)

我觉得这是关系到Google Play的服务更新。有没有人能帮助我在这个问题上？

I think this is related to google play services update. Is anyone able to help me out on this issue?

只是为了证实该问题与播放服务，我已成功地从一个线程调用AdWorker crashlytics得到这样的：

Just to confirmed that the issue is related to play service I have managed to get this from crashlytics from a thread called AdWorker:

thread
   at java.lang.Object.wait(Object.java)
   at java.lang.Thread.parkFor(Thread.java:1231)
   at sun.misc.Unsafe.park(Unsafe.java:323)
   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:157)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:813)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:973)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1282)
   at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:207)
   at zo.a(SourceFile:147)
   at zo.a(SourceFile:170)
   at aeh.a(SourceFile:120)
   at afw.run(SourceFile:14)
   at afy.run(SourceFile:30)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
   at java.lang.Thread.run(Thread.java:856)

这是不正确的地方......但是没有任何地方都去哪里举报他们。

it is not the right place... but there is no place at all where to report them

例外数它有双从7月1日，它现在几乎是3倍这是什么6月27日。

Number of exceptions it has double from 1 july, it is now almost 3 times what it was the 27th of june.

发行：谷歌Android code项目

最后回复来自谷歌我们知道这些崩溃和正在修复。我们希望能推出这些修补程序，在未来两个星期。 （7月7日）

Last reply from google "We're aware of these crashes and are working on fixes. We hope to push out these fixes in the next week or two." (July 7th)

推荐答案

发现这个解决方案由马特乌什Matela在https://groups.google.com/forum/#!topic/google-admob-ads-sdk/DkjtCx_Zvn8.

Found this solution by Mateusz Matela at https://groups.google.com/forum/#!topic/google-admob-ads-sdk/DkjtCx_Zvn8.

我试图在摩托罗拉DEFY +坠毁，从这个bug三分之二的时间。看来即使assositated这个错误的警告出现在日志中工作。它甚至说，AdWorker线程抛出的异常。我的广告，甚至在继续使用的应用程序reappeard。

I have tried on a Motorola DEFY+ that crashed from this bug two out of three times. It seems to work even when the warnings assositated with this bug appears in the log. It even says "AdWorker thread thrown an exception". My ads even reappeard when continuing to use the app.

final UncaughtExceptionHandler defaultHandler = Thread.getDefaultUncaughtExceptionHandler();
Thread.setDefaultUncaughtExceptionHandler(new UncaughtExceptionHandler() {
        @Override
        public void uncaughtException(Thread thread, Throwable ex) {
            if (thread.getName().startsWith("AdWorker")) {
                Log.w("ADMOB", "AdWorker thread thrown an exception.", ex);
            } else if (defaultHandler != null) {
                defaultHandler.uncaughtException(thread, ex);
            } else {
                throw new RuntimeException("No default uncaught exception handler.", ex);
            }
        }
});