my “primary” build was for Google Play, and includes licensing and the com.android.vending.CHECK_LICENSE permission in build.settings.
if I now intend to create a build for Amazon, am I ok leaving that permission in, or should it be removed? i guess the question boils down to: would it cause any problems if left in?
i already have the actual license-checking code conditional upon system.getInfo(“targetAppStore”) since it only applies to google.
while it would seem “simple enough” to remove/comment-out the unneeded permission, it further complicates my (already complicated) build process by requiring yet another customized build.settings (i already have 2).
so purely for ease of any future maintenance am wondering if i can just ignore that extra/unneeded permission and leave it in, or if Amazon is going to flag it as something unsupported or whatever.
and just a quick survey: is it expected (or not) to create a build *specifically* for Amazon? that is, is it expected that an apk for google play will be publishable *as is* on amazon? and if so, any limitations? that is, under what conditions might that single google apk *not* be valid for amazon? (my app doesn’t use ads or google play services, but assuming appropriate run-time ad-switching logic were in place based on app store, q is: any *other* such run-time switching that might be necessary?) thanks!