@matrix2000 what happens if you try and call your function and don’t specify the appID?
Everyone,
As of daily build 1101, we’ve modified the native.showPopup() function to show the app store that the app is targeting. This will prevent the problem where Corona picks the wrong app store on devices that have multiple app stores installed.
http://developer.coronalabs.com/release/2013/1101
If you are building with release version #1076, then you can work-around this issue by launching the app store like this…
local options = { iOSAppId = "my.ios.id", nookAppEAN = "my.nook.ean", supportedAndroidStores = { system.getInfo("targetAppStore") }, } native.showPopup("appStore", options)
Notice that the above code restricts the supported stores by the targeted app store.
One more thing to note. If your Android app is not targeting an app store (ie: target app store is set to “none”), then the native.showPopup() function will fallback to the old behavior where it is forced to “guess” which app store to launch.
In this case, Corona first checks which app store installed your app and will launch that app store’s dialog by default.
If your app was not installed by an app store (ie: it was side loaded), then Corona has no choice but to pick the first app store it finds installed on the device. That’s the issue that you guys are running into with the Amazon app review process. The reviewers are side loading your app via “adb install” and their test devices have both Google Play and Amazon App Store installed… and Corona is happening to pick the wrong store. There is no way for Corona to guess correctly if you set the target store to “none”, in which case, it is up to you to tell it which store to favor via the “supportedAndroidStores” property. At least as of daily build #1101. Our native.showPopup() function was written before we added the ability to target an app store in the Android build window, which is why it was always guessing (and sometimes wrongly) in older builds, because we’ve only recently leveraged the target app store.
In any case, I hope the above helps.
Fixed with release 1101.
I am having a similar problem. My app was rejected by Amazon because it is launching the Google Play store and not Amazons. Are there any answers on this?
From my xp this happens when you build your build targeting android store. What happens if you target Amazon’s is that the native show popup does no action (at least in my side) that’s the problem I’m wating an answer for since long in this thread.
@matrix2000 what happens if you try and call your function and don’t specify the appID?
Everyone,
As of daily build 1101, we’ve modified the native.showPopup() function to show the app store that the app is targeting. This will prevent the problem where Corona picks the wrong app store on devices that have multiple app stores installed.
http://developer.coronalabs.com/release/2013/1101
If you are building with release version #1076, then you can work-around this issue by launching the app store like this…
local options = { iOSAppId = "my.ios.id", nookAppEAN = "my.nook.ean", supportedAndroidStores = { system.getInfo("targetAppStore") }, } native.showPopup("appStore", options)
Notice that the above code restricts the supported stores by the targeted app store.
One more thing to note. If your Android app is not targeting an app store (ie: target app store is set to “none”), then the native.showPopup() function will fallback to the old behavior where it is forced to “guess” which app store to launch.
In this case, Corona first checks which app store installed your app and will launch that app store’s dialog by default.
If your app was not installed by an app store (ie: it was side loaded), then Corona has no choice but to pick the first app store it finds installed on the device. That’s the issue that you guys are running into with the Amazon app review process. The reviewers are side loading your app via “adb install” and their test devices have both Google Play and Amazon App Store installed… and Corona is happening to pick the wrong store. There is no way for Corona to guess correctly if you set the target store to “none”, in which case, it is up to you to tell it which store to favor via the “supportedAndroidStores” property. At least as of daily build #1101. Our native.showPopup() function was written before we added the ability to target an app store in the Android build window, which is why it was always guessing (and sometimes wrongly) in older builds, because we’ve only recently leveraged the target app store.
In any case, I hope the above helps.
Fixed with release 1101.