New AdMob - app crash

Solar2D Monetization (in-app purchases, ads, etc.)
#1

I am trying to update my apps to the new AdMob V2, but on my two tablets with Android 4.0, my apps crashed with following error:

W/Ads(7790): Interrupted during GADSignals creation.                                                 

W/Ads(7790): java.lang.InterruptedException                                                          

W/Ads(7790): at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterrupt

W/Ads(7790): at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptib

W/Ads(7790): at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:207)            

W/Ads(7790): at zo.a(SourceFile:147)                                                          

W/Ads(7790): at zo.a(SourceFile:170)                                                          

W/Ads(7790): at aeh.a(SourceFile:120)                                                         

W/Ads(7790): at afw.run(SourceFile:14)                                                        

W/Ads(7790): at afy.run(SourceFile:30)                                                        

W/Ads(7790): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076

W/Ads(7790): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569

W/Ads(7790): at java.lang.Thread.run(Thread.java:856)                                         

W/dalvikvm(7790): threadid=21: thread exiting with uncaught exception (group=0x40c161f8)             

E/AndroidRuntime(7790): FATAL EXCEPTION: AdWorker #2                                                 

E/AndroidRuntime(7790): java.lang.NullPointerException                                               

E/AndroidRuntime(7790): at zo.a(SourceFile:172)                                                  

E/AndroidRuntime(7790): at aeh.a(SourceFile:120)                                                 

E/AndroidRuntime(7790): at afw.run(SourceFile:14)                                                

E/AndroidRuntime(7790): at afy.run(SourceFile:30)                                                

E/AndroidRuntime(7790): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j

E/AndroidRuntime(7790): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.

E/AndroidRuntime(7790): at java.lang.Thread.run(Thread.java:856)                                 

W/ActivityManager(345):   Force finishing activity r.intent.getComponent().flattenToShortString()    

In my code I am changed only build settings to replace  “CoronaProvider.ads.admob” with “plugin.google.play.services”.

This happened in two different aps and only on devices (tablets) with Android 4.0 (on Android 2.3 and 4.4 (phones) seems to be OK), sometimes these apps working without problems, banners are displayed but usually after app launch banners are not displayed and after tap in menu options occurs app crash. Tested on Corona 2014.2347 and 2014.2382. I am using also Facebook plugin.

#2

I’m having a similar issue with adMob V2. I don’t have the console output yet to compare errors, but it works fine on one and crashes on another. The one that is crashing has Android 4.2.2. The one working has 4.0. It’s frustrating, as I can’t submit the update with the new adMob plugin until I know it’s working. I should have a cable in a couple days to connect the problem tablet to my computer and get console output. I’ll let you know if it’s similar to what you have.

#3

Do you using facebook in your app? In my app without facebook, the new AdMob working well, with facebook the problem is as above.

#4

I’m not using Facebook. The only other plugins I’m using are iAds (for iOS) and game network. I’ll try removing those to see if there’s any difference.

#5

Can you produce a small sample project and file a bug report using the “Report a bug” feature at the top of the page.  Engineering can’t reproduce this and they need to see it happening.  Please make sure to include the build.settings and config.lua files and create a .zip file to upload.

Thanks

Rob

#6

This problem still exist.

I am created bug submission and I hope that Corona look on this issue.

#7

The problem is still not resolved.

Corona not answered to my bug submission (the same as my previous another bug submission - these submissions are going to dev:null ???)

Yesterday Amazon reject my app due to this reason:

Observation:- Feature/ Buttons not responding/working :
Step to reproduce error:
1.Install and Launch the App.
2.Play the game.
3.Tap on share.
4.Unable to share score on Facebook.

With the old AdMob everything working well (with changes only in the build settings), but with “NEW” adMob v2 this is not working. This problem is related with Facebook, which hangs app when user trying to share a score.

#8

What is the bug ID number?

#9

Where I can find this number? I didn’t received any confirmation after my bug submission. Submission date: 20.08.2014

#10

You should have gotten an email from the bug reporter that would have the ID number in it.

#11

Unfortunately I haven’t received any confirmation email :frowning:

#12

@info09, I only see one active bug that you have filed, and its about a Graphics 2.0 performance issue.  I’m afraid your bugs have not been submitted.  I found one open bug regarding Facebook and AdMob together.  That bug seems to be around using setActivityIndicator.  There are several forum posts and I’ve asked for bug reports on this.

If we can’t get the bug report, with a sample app that demonstrates the problem. the Engineers absolutely have to have this.  It must also include a the build.settings and config.lua being used in the problem. 

Rob

#13

I’m not using setActivityIndicator.

Today I’m created new bug submission - Case: 35572 (this time I’m received confirmation email).

Today I’m also tested app on the newest Corona build (2014.2432) with facebook as a plugin but this problem still exist.

#14

I’m having a similar issue with adMob V2. I don’t have the console output yet to compare errors, but it works fine on one and crashes on another. The one that is crashing has Android 4.2.2. The one working has 4.0. It’s frustrating, as I can’t submit the update with the new adMob plugin until I know it’s working. I should have a cable in a couple days to connect the problem tablet to my computer and get console output. I’ll let you know if it’s similar to what you have.

#15

Do you using facebook in your app? In my app without facebook, the new AdMob working well, with facebook the problem is as above.

#16

I’m not using Facebook. The only other plugins I’m using are iAds (for iOS) and game network. I’ll try removing those to see if there’s any difference.

#17

Can you produce a small sample project and file a bug report using the “Report a bug” feature at the top of the page.  Engineering can’t reproduce this and they need to see it happening.  Please make sure to include the build.settings and config.lua files and create a .zip file to upload.

Thanks

Rob

#18

This problem still exist.

I am created bug submission and I hope that Corona look on this issue.

#19

The problem is still not resolved.

Corona not answered to my bug submission (the same as my previous another bug submission - these submissions are going to dev:null ???)

Yesterday Amazon reject my app due to this reason:

Observation:- Feature/ Buttons not responding/working :
Step to reproduce error:
1.Install and Launch the App.
2.Play the game.
3.Tap on share.
4.Unable to share score on Facebook.

With the old AdMob everything working well (with changes only in the build settings), but with “NEW” adMob v2 this is not working. This problem is related with Facebook, which hangs app when user trying to share a score.

#20

What is the bug ID number?