This is not appears on IOS.
I was having problems on iOS and assumed I was caught in this issue with the SDK problem. I went back in and recompiled and tested and it worked. I may have been having a problem based on creating the ad units and then testing on the same day. I didn’t actually change any of the code related to showing videos.
I’m getting rewarded video on iOS now. I will test on Android probably next week. Glad to find out that at the very least this should work on iOS.
Hi Rob,
after adding new applicationChildElements to build.settings admob rewarded video worked fine over the last week with some updated apps but today I’ve tried them again and I see only a black screen at the end of the video. (no errors while debugging)
I’m using Corona 64 bits 3498
Can you please check?
Thanks
I’m not sure if I did it ok.
What do I have to write as APPLICATION_ID?
the bundle I use to build for Google Play?
[[
<meta-data android:name=“com.google.android.gms.ads.APPLICATION_ID”
android:value=" ca-app-pub-zzzzzzzzzzz~xxxxxxxxxx"/>
]],
Is this happening on all rewarded video ads? Are you using test ads or live ads?
Rob
Only with rewarded ads.
I have just tested again with the same published app and now it works.
Ghosts?
Can you please confirm what do I have to put in this line?
com.google.android.gms.ads.APPLICATION_ID
Here is my complete build.settings:
settings = { orientation = { default ="landscapeRight", supported = {"landscapeRight", "landscapeLeft"}, }, ["plugin.admob"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true } }, }, iphone = { xcassets = "Images.xcassets", plist = { NSCalendarsUsageDescription = "", NSAppTransportSecurity = { NSAllowsArbitraryLoads=true }, NSPhotoLibraryUsageDescription = "This app does not access the photo library.", NSCameraUsageDescription = "This app does not use the camera.", UILaunchStoryboardName = "LaunchScreen", } }, android = { googlePlayGamesAppId = "xxxxxxxxxxxxxxx", usesPermissions = { "com.android.vending.BILLING", "com.android.vending.CHECK\_LICENSE", "android.permission.INTERNET", "android.permission.VIBRATE", "android.permission.WRITE\_EXTERNAL\_STORAGE", "android.permission.ACCESS\_NETWORK\_STATE", -- needed for the vungle plugin }, supportsScreens = { resizeableActivity = false, smallScreens = true, normalScreens = true, largeScreens = true, xlargeScreens = true, }, applicationChildElements = { [[\<meta-data android:name="com.google.android.gms.ads.APPLICATION\_ID" android:value="ca-app-pub-xxxxxxxxxxxxxxxx~yyyyyyyyyy"/\> -- replace with your app id. See: https://goo.gl/fQ2neu]], } }, window = { defaultMode = "normal", resizable = true, minViewWidth = 960, minViewHeight = 640, enableCloseButton = true, enableMinimizeButton = true, enableMaximizeButton = true, suspendWhenMinimized = true, titleText = { -- The "default" text will be used if the system is using a language and/or -- country code not defined below. This serves as a fallback mechanism. default = "Alien Invasion", } }, excludeFiles = { -- Exclude all files at paths which end with "secret.txt" -- Exclude all Android icon files and .ogg files in the "music" directory ios = { "Icon-\*dpi.png", }, -- Exclude iOS "retina" image files and .m4a files in the "music" directory android = { "Icon.png", "\*@2x.png", "LaunchScreen\*" }, -- Exclude unnecessary assets from macOS desktop apps osx = { "Default\*.png", "Icon\*.png", "Icon\*.ico", "Icon\*.icns" }, -- Exclude unnecessary assets from Win32 desktop apps win32 = { "Default\*.png", "Icon\*.png", "Icon\*.ico", "Icon\*.icns" }, -- Exclude all Android icon files and .ogg files in the "music" directory tvos = { "Icon-\*dpi.png", "music/\*.ogg" }, }, }
So, this line keeps as it is. Nothing to change.
Only the next line with admob app id is where the numbers go.
Thanks Rob
I’ve been testing admob rewarded for a while and some times the ad finishes ok but some times it finishes with black screen. Don’t really know why but it’s not perfectly working on Android with 64 bit.
I see a big number of error in Android vitals with this last version:
java.util.concurrent.TimeoutException :
at com.google.android.gms.ads.internal.webview.j.k (com.google.android.gms.policy_ads_fdr_dynamite@20300002@20300002.251657827.251657827:3)
at com.google.android.gms.ads.internal.webview.v.destroy (com.google.android.gms.policy_ads_fdr_dynamite@20300002@20300002.251657827.251657827:4)
at com.google.android.gms.ads.internal.webview.t.destroy (com.google.android.gms.policy_ads_fdr_dynamite@20300002@20300002.251657827.251657827:10)
at com.google.android.gms.ads.nonagon.ad.interstitial.b.finalize (com.google.android.gms.policy_ads_fdr_dynamite@20300002@20300002.251657827.251657827:5)
at java.lang.Daemons$FinalizerDaemon.doFinalize (Daemons.java:209)
at java.lang.Daemons$FinalizerDaemon.run (Daemons.java:192)
at java.lang.Thread.run (Thread.java:818)
I read 2 threads discussing the issue, and it seems to be something on google’s backend, because it’s affected people with apps that havent changed their app or SDKs for months. A google employee mentioned their next release will fix it.
https://github.com/googleads/googleads-mobile-android-examples/issues/170
https://groups.google.com/forum/#!topic/google-admob-ads-sdk/cbr_oV4Yzfg
The last post on this thread mentions …
“I solved the problem by not calling “interstitial.loadad() (for loading next ad)” directly after interstitial.show() . So don’t load next ad until your shown ad is closed.”
That might be worth trying to see if it fixes this issue.
In the thread the issue seems to be affecting around 5% of session, and affects both rewarded and interstitial, and affect people with versions of GMS back to 15.0.1.
Since, the problem existed before 64bit betas, and the threads don’t mention it being 64-bit only. I’m assuming the problem is on 32 and 64bit.
And another video: https://drive.google.com/file/d/1HfjpTR5KzkAwyyFiMeCu9klSRvzxJ3q1/view?usp=sharing
Yes I have the same problem past few days. Do you see this in non-Corona games?
In non-Corona games we have no problem.
I’ve reached out to my Google account manager and things changed this week which has clearly broken the AdMob plugin.
It doesn’t help that the SDK is many versions out of date!
Corona need to urgently fix the issue.
bump!
I’m working on adding AdMob’s rewardedVideo to a client’s app in the next few days. Are there any updates on this?
No fix until 64 bit is finished… so at least 1 -2 months I’d say.
damn did not know about this til i read this… just checked my apps same thing…
Developers we need an update…