Hi Rob,
First, we can’t target Google and publish that to Amazon, because we already have 7,000 monthly Amazon users, which target the Amazon store and most have Kindle Fire devices. Also, if we target to Google, we won’t be able to have in-app purchases from the Amazon store. In short - this is not really an option.
Second, as I stated above in the thread, I already tried to go to the documentation of each plugin we use and keep only the ones that either have [“android-kindle”]=true in the supportedPlatforms line or didn’t have a supportedPlatforms line at all. After doing that, my plugin list was similar to the one I wrote above, only I removed Chartboost, AppLovin, Flurry and Kochava as well. Even after doing that, I still got the error message. Meaning, there is at least one plugin in that list above that includes Google Play Services, even though it is supported on Amazon.
This brings up another problem - since Chartboost, AppLovin and Kochava all have support for the Amazon store in their SDK, why doesn’t the plugin officially support it?
Up until now, we have been using these 3 plugins in our Amazon targeted app, and they all work perfectly fine - why should we suddenly have to remove them?
And finally, we already have in place all the implementation to handle any Kindle Fire exceptions (e.g. no advertising id).
We’ve been using Corona for 3 years, and have been publishing to Amazon for a year and a half already, and having Google Play Services included in the apk was never an issue. What changed? Why should plugins that worked up until now suddenly stop working?
I don’t understand why this error checking can’t simply be removed, so everything can return to the way it was before.
If this issue is not resolved, we will not be able to continue support for Amazon users, and it’s as if Corona Labs is dropping the support for Amazon as a target store.