Hello,
We recently noticed an issue where our banner ads (Admob) were not displaying on Amazon devices. Banners do work perfectly fine on Google Play and iOS, and the code for the ads is exactly the same in all 3 builds.
Our build settings is set up with this line in plugins, based on current documentation:
[“plugin.google.play.services”] = { publisherId = “com.coronalabs”,supportedPlatforms = { iphone=true, android=true }},
Android devices that do not have the Google Play app on them do not support “Google Play Services”, “Google Play Game Services”, “AdMob”, GCM (Google Cloud Message) push notifications, Google in-app purchases, etc. These are Google Play exclusive features and only work if the Google Play app is installed. You should only be using these features for apps distributed by the “Google Play” app store, because then you’re guaranteed that these feature exist on your customers’ devices.
So, for Amazon devices, you’ll have to use a 3rd party ad solution.
And if you’re doing in-app purchases and game networking, you’ll have to use Amazon’s equivalent plugins.
Hold on. While I’m right that “Google Play Services” is not available on an Amazon device such as a Fire Tablet, Google’s developers do claim that AdMob is supposed to still work on those devices by falling-back to requesting the ads over the network. So, I may be wrong about AdMob. But you’re not alone in this issue. See the issue posted to Google’s support team via the link below. This person is having the same issue as you. Google’s response in that link is to contact their support group, but that’s not quite the answer you’re looking for.
https://groups.google.com/forum/#!topic/google-admob-ads-sdk/wLjHAmBDatU
But that said, a 3rd party ad solution is still a valid solution.
Strange, because Admob did used to work for us before on all 3 stores, it just stopped working with banners recently. We’ll try to find alternate solutions though.
If you look at that link I gave you, it’s happening to others as well. Google’s servers are not sending ad responses, which suggests that their fallback mechanism for the cases where Google Play Services is unavailable isn’t working right now. So, it’s probably an issue on their end and they missed it by mistake since Google is most likely to test this on devices having Google Play.
Android devices that do not have the Google Play app on them do not support “Google Play Services”, “Google Play Game Services”, “AdMob”, GCM (Google Cloud Message) push notifications, Google in-app purchases, etc. These are Google Play exclusive features and only work if the Google Play app is installed. You should only be using these features for apps distributed by the “Google Play” app store, because then you’re guaranteed that these feature exist on your customers’ devices.
So, for Amazon devices, you’ll have to use a 3rd party ad solution.
And if you’re doing in-app purchases and game networking, you’ll have to use Amazon’s equivalent plugins.
Hold on. While I’m right that “Google Play Services” is not available on an Amazon device such as a Fire Tablet, Google’s developers do claim that AdMob is supposed to still work on those devices by falling-back to requesting the ads over the network. So, I may be wrong about AdMob. But you’re not alone in this issue. See the issue posted to Google’s support team via the link below. This person is having the same issue as you. Google’s response in that link is to contact their support group, but that’s not quite the answer you’re looking for.
https://groups.google.com/forum/#!topic/google-admob-ads-sdk/wLjHAmBDatU
But that said, a 3rd party ad solution is still a valid solution.
Strange, because Admob did used to work for us before on all 3 stores, it just stopped working with banners recently. We’ll try to find alternate solutions though.
If you look at that link I gave you, it’s happening to others as well. Google’s servers are not sending ad responses, which suggests that their fallback mechanism for the cases where Google Play Services is unavailable isn’t working right now. So, it’s probably an issue on their end and they missed it by mistake since Google is most likely to test this on devices having Google Play.