Recently updated a device android 6.0 and vungle test ads stopped working. Android 4.4 and android 5.0 have no problems with test ads. Below are some of the errors found in the debug log. Basically on the “adStart” check I get the error msg return of “no cached or streaming ad available” in android 6.0, but the same app on other older android OS works fine and shows test ads. The error logs do indicate something about processing ad.id but the id’s are fine unless it’s an issue on vungle’s side with test ads. Note: live ads work fine on android 6.0.
10-27 16:20:09.919: V/Corona(27839): > Class.forName: CoronaProvider.ads.vungle.LuaLoader
10-27 16:20:09.919: V/Corona(27839): < Class.forName: CoronaProvider.ads.vungle.LuaLoader
10-27 16:20:09.919: V/Corona(27839): Loading via reflection: CoronaProvider.ads.vungle.LuaLoader
10-27 16:20:13.429: E/VunglePrepare(27839): error processing ad.id: 5494b417107fe69e24ac6011|5494b417107fe69e24ac6012|test
10-27 16:20:13.429: E/VunglePrepare(27839): java.lang.RuntimeException: could not update failed status
10-27 16:20:13.429: E/VunglePrepare(27839): error processing ad.id: 5494b417107fe69e24ac6011|5494b417107fe69e24ac6012|test
10-27 16:20:13.429: E/VunglePrepare(27839): java.lang.RuntimeException: could not update failed status
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.afi.a(vungle:77)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.afi.a(vungle:31)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.aiu$a.a(vungle:69)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.ajb$d.a(vungle:148)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.aiu$a.a(vungle:77)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.air$a.a(vungle:76)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.ajb$d.a(vungle:148)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.aiu$a.a(vungle:77)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.aiq$a.a(vungle:101)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.ajb$d.a(vungle:148)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.aiu$a.a(vungle:77)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.ajb$d.a(vungle:148)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.aiu$a.a(vungle:77)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.ajb$d.a(vungle:148)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.aiu$a.a(vungle:77)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.ajd$1$1.a(vungle:53)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.alm$2.a(vungle:235)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.aja$1$3.d(vungle:87)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.ajj$a$2.d(vungle:189)
10-27 16:20:13.429: E/VunglePrepare(27839): at com.vungle.publisher.ajp.run(vungle:55)
10-27 16:20:13.429: E/VunglePrepare(27839): at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:423)
10-27 16:20:13.429: E/VunglePrepare(27839): at java.util.concurrent.FutureTask.run(FutureTask.java:237)
10-27 16:20:13.429: E/VunglePrepare(27839): at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:154)
10-27 16:20:13.429: E/VunglePrepare(27839): at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:269)
10-27 16:20:13.429: E/VunglePrepare(27839): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
10-27 16:20:13.429: E/VunglePrepare(27839): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
10-27 16:20:13.429: E/VunglePrepare(27839): at java.lang.Thread.run(Thread.java:818)
Still awaiting feedback from vungle on this issue but wondering if anyone has the same issue with test ads on android 6.0.