After updating to simulator version 2016.3007, when targeting Amazon, the app does not launch.
After the splash I see an error message saying:
Corona: Developer Error
<App Name> does not target the Google Play store, but includes Google Play Services.
…
Please remove Google Play Services from builds that do not target Google Play.
I went over my build.settings file and removed all the plugins that might not work on Amazon, yet I still get this message.
Here is our plugin list from build.settings:
["plugin.facebook.v4"] = { publisherId = "com.coronalabs" }, ["plugin.google.iap.v3"] = { publisherId = "com.coronalabs", supportedPlatforms = { android=true } }, ["plugin.amazon.iap"] = { publisherId = "com.coronalabs", supportedPlatforms = { ["android-kindle"]=true }, }, ["plugin.flurry.analytics"] = { publisherId = "com.coronalabs", }, ["plugin.googleAnalytics"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true } }, ["plugin.kochava"] = { publisherId = "com.coronalabs", }, ["plugin.openssl"] = { publisherId = "com.coronalabs" }, ["plugin.advertisingId"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true } }, ["plugin.OneSignal"] = { publisherId = "com.onesignal", }, ["plugin.notifications"] = { publisherId = "com.coronalabs", }, ["plugin.pasteboard"] = { publisherId = "com.coronalabs", }, ["plugin.utf8"] = { publisherId = "com.coronalabs", }, ["plugin.iCloud"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true }, }, ["CoronaProvider.native.popup.social"] = { publisherId = "com.coronalabs", }, ["CoronaProvider.native.popup.activity"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true } }, ["plugin.CoronaSplashControl"] = { publisherId = "com.coronalabs" }, ["plugin.chartboost"] = { publisherId = "com.coronalabs", }, ["plugin.applovin"] = { publisherId = "com.coronalabs", }, ["CoronaProvider.ads.vungle"] = { publisherId = "com.vungle", supportedPlatforms = { iphone=true, android=true } }, ["plugin.supersonic"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true } }, ["plugin.adbuddiz"] = { publisherId = "com.adbuddiz", supportedPlatforms = { iphone=true, android=true } }, ["plugin.fbAudienceNetwork"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true } }, ["plugin.pollfish"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true } },
I tried to remove also Chartboost, AppLovin, Flurry, Facebook and Kochava, but I still see that error…
Can someone, once and for all, tell us which plugins should not work on amazon?
Analytics: Flurry, Google Analytics, Game Analytics, Kochava
Ads: Chartboost, AppLovin, Vungle, FBAN, Supersonic, AdBuddiz, Pollfish
I know Kochava’s, Chartboost’s and AppLovin’s SDKs support Amazon (it’s been working for us up until now), so I would expect the plugins to work on Amazon as well.
Also, this error should be removed, since a lot of Amazon store users still have the Google Play Store on their devices, it’s only the Kindle users that cannot have it.
For example, up until now we’ve been using Vungle on Amazon targeted apps on devices that are not Kindle Fire. There is no reason to stop supporting it now…
Please help us identify who is including the Google Play Services and please remove this error so we can continue using all the providers we’ve been using.
Thanks
Can someone, once and for all, tell us which plugins should not work on amazon?
Analytics: Flurry, Google Analytics, Game Analytics, Kochava
Ads: Chartboost, AppLovin, Vungle, FBAN, Supersonic, adbuddiz, pollfish
I know Kochava’s, Chartboost’s and AppLovin’s SDK supports Amazon (it’s been working for us up until now), so I would expect the plugins to work on Amazon as well.
Also, this error should be removed, since a lot of Amazon store users still have the Google Play Store on their devices, it’s only the Kindle users that cannot have it.
For example, up until now we’ve been using Vungle on Amazon targeted apps on devices that are not Kindle Fire. There is no reason to stop supporting it now…