Corona Ads - Random White Screen During Banner Ad Display

Corona Marketplace Corona Ads
#1

I am testing Corona Ads and once in awhile a white screen will appear that covers the entire display that only a force close will get rid of. Even though I am calling for a bottom banner it makes one think that an interstitial is about to appear but it never does; only the white screen.

After a few debugs I found that when it occurs “mobfox” is the ad network. That may or may not have anything to do with it but the banner ads that are working properly seem to show no ad network ([network] => “”). I have opened a case (5975212) with ads AT coronalabs.com.

Below are the results of the ad listener when it occurs.

09-21 08:42:10.149 31518 31535 I Corona  : coronaAdsListener, request
09-21 08:42:10.149 31518 31535 I Corona  : print_r
09-21 08:42:10.149 31518 31535 I Corona  : table: 0xb8439240 {
09-21 08:42:10.149 31518 31535 I Corona  :   [placementId] => “bottom-banner-320x50”
09-21 08:42:10.159 31518 31535 I Corona  :   [isError] => false
09-21 08:42:10.159 31518 31535 I Corona  :   [phase] => “request”
09-21 08:42:10.159 31518 31535 I Corona  :   [provider] => “coronaAds”
09-21 08:42:10.159 31518 31535 I Corona  :   [name] => “adsRequest”
09-21 08:42:10.159 31518 31535 I Corona  : }

09-21 08:42:15.939 31518 31535 I Corona  : coronaAdsListener, found
09-21 08:42:15.939 31518 31535 I Corona  : print_r
09-21 08:42:15.939 31518 31535 I Corona  : table: 0xb83c4ea0 {
09-21 08:42:15.939 31518 31535 I Corona  :   [placementId] => “bottom-banner-320x50”
09-21 08:42:15.939 31518 31535 I Corona  :   [identifier] => “”
09-21 08:42:15.949 31518 31535 I Corona  :   [isError] => false
09-21 08:42:15.949 31518 31535 I Corona  :   [phase] => “found”
09-21 08:42:15.949 31518 31535 I Corona  :   [network] => “mobfox”
09-21 08:42:15.949 31518 31535 I Corona  :   [provider] => “coronaAds”
09-21 08:42:15.949 31518 31535 I Corona  :   [name] => “adsRequest”
09-21 08:42:15.949 31518 31535 I Corona  : }

09-21 08:42:15.949 31518 31535 I Corona  : coronaAdsListener, shown
09-21 08:42:15.949 31518 31535 I Corona  : print_r
09-21 08:42:15.949 31518 31535 I Corona  : table: 0xb82d7b08 {
09-21 08:42:15.949 31518 31535 I Corona  :   [placementId] => “bottom-banner-320x50”
09-21 08:42:15.949 31518 31535 I Corona  :   [identifier] => “”
09-21 08:42:15.949 31518 31535 I Corona  :   [isError] => false
09-21 08:42:15.949 31518 31535 I Corona  :   [phase] => “shown”
09-21 08:42:15.949 31518 31535 I Corona  :   [network] => “mobfox”
09-21 08:42:15.949 31518 31535 I Corona  :   [provider] => “coronaAds”
09-21 08:42:15.949 31518 31535 I Corona  :   [name] => “adsRequest”
09-21 08:42:15.959 31518 31535 I Corona  : }

Thanks ahead of time,

Scott

#2

Hi, I’m seeing the same exact problem. I thought perhaps it was something I was doing wrong in my application, but then I saw it happens even with the Corona sample app:  https://github.com/coronalabs/plugins-sample-coronaAds.  

When that sample app is installed on my Galaxy S7 it often just brings up a white screen when I click on one of the buttons.  And like you said, the only way to get rid of it is to force stop that app. After restarting that app several times it sometimes works without the white screen. Has anyone found a solution? 

#3

Please report the issue to support AT coronalabs.com

Be sure to include as much information as possible (Device, OS, version of Corona, OS you’re building from, the console log. On Android, just run “adb logcat” without any extra parameters.

Thanks

Rob

#4

I have opened a case (5975212) with ads AT coronalabs.com.

Thanks,

Scott

#5

Hi All,  Do we know if this issue has been resolved? I’ve been afraid to go back to using coronaads because of the blank white screen stopping my app in its tracks. Is there a way to track the outcome of the case# 5975212 that was mentioned above?

It was happening with the Corona sample app:  https://github.com/coronalabs/plugins-sample-coronaAds too so I guess it wasn’t just my code.  I’m doing build from Corona simulator Build: 2016.2906 on Windows 7, PC, and deploying to Android Marshmallow on a Samsung Galaxy S7.  

Thanks very much

#6

The ticket number does not show that a bug report was filed. The Corona technician specifically asked for a sample app that has the problem after other trouble shooting didn’t solve the problem.  We need a simple test case that shows the problem (main.lua, config.lua, build.settings and any other assets needed to build, install the app on a device, run it and see the error) put in a .zip file and use the “Report a bug” link at the top of the file.

Rob

#7

Thank for the info Rob. It is much appreciated.

This is a random issue that we cannot reproduce on demand, it just happens sporadically as ads are pushed down to the app. It may go days without occurring or just minutes. The Corona sample app is as good a test as any since it occurs there as well. 

However, it has been my experience that when the issue does occur, “mobfox” is always listed as the “network” parameter. See the output in my original post above for the details. I believe if engineering could concentrate on the “mobfox” network they can most likely start reproducing the error on demand then find resolution. My first guess is “mobfox” is sending down some sort of corrupt ad. I will say though that I have not seen the error in a few days now so maybe “mobfox” cleaned up their act! I just don’t know.

Thanks again for all your help and all that you do to support our community.

#8

In that case, you probably should continue the conversation with the support folks through the email thread.

Rob

#9

Hi gsglawson, please let us know what you find out if they get back to you on your email thread. I’ve been afraid to go back to coronaads since it froze up everything when it happens.

Coronaads seemed to pay more than admob (my current ad provider), are you finding that to be the case too?

#10

Hi, I’m seeing the same exact problem. I thought perhaps it was something I was doing wrong in my application, but then I saw it happens even with the Corona sample app:  https://github.com/coronalabs/plugins-sample-coronaAds.  

When that sample app is installed on my Galaxy S7 it often just brings up a white screen when I click on one of the buttons.  And like you said, the only way to get rid of it is to force stop that app. After restarting that app several times it sometimes works without the white screen. Has anyone found a solution? 

#11

Please report the issue to support AT coronalabs.com

Be sure to include as much information as possible (Device, OS, version of Corona, OS you’re building from, the console log. On Android, just run “adb logcat” without any extra parameters.

Thanks

Rob

#12

I have opened a case (5975212) with ads AT coronalabs.com.

Thanks,

Scott

#13

Hi All,  Do we know if this issue has been resolved? I’ve been afraid to go back to using coronaads because of the blank white screen stopping my app in its tracks. Is there a way to track the outcome of the case# 5975212 that was mentioned above?

It was happening with the Corona sample app:  https://github.com/coronalabs/plugins-sample-coronaAds too so I guess it wasn’t just my code.  I’m doing build from Corona simulator Build: 2016.2906 on Windows 7, PC, and deploying to Android Marshmallow on a Samsung Galaxy S7.  

Thanks very much

#14

The ticket number does not show that a bug report was filed. The Corona technician specifically asked for a sample app that has the problem after other trouble shooting didn’t solve the problem.  We need a simple test case that shows the problem (main.lua, config.lua, build.settings and any other assets needed to build, install the app on a device, run it and see the error) put in a .zip file and use the “Report a bug” link at the top of the file.

Rob

#15

Thank for the info Rob. It is much appreciated.

This is a random issue that we cannot reproduce on demand, it just happens sporadically as ads are pushed down to the app. It may go days without occurring or just minutes. The Corona sample app is as good a test as any since it occurs there as well. 

However, it has been my experience that when the issue does occur, “mobfox” is always listed as the “network” parameter. See the output in my original post above for the details. I believe if engineering could concentrate on the “mobfox” network they can most likely start reproducing the error on demand then find resolution. My first guess is “mobfox” is sending down some sort of corrupt ad. I will say though that I have not seen the error in a few days now so maybe “mobfox” cleaned up their act! I just don’t know.

Thanks again for all your help and all that you do to support our community.

#16

In that case, you probably should continue the conversation with the support folks through the email thread.

Rob

#17

Hi gsglawson, please let us know what you find out if they get back to you on your email thread. I’ve been afraid to go back to coronaads since it froze up everything when it happens.

Coronaads seemed to pay more than admob (my current ad provider), are you finding that to be the case too?