Thank you, Luciane! I appreciate you letting me know. I’ll keep using the system.openURL for Apple App Store, and use the new API for NOOk when it’s ready then.
Cheers,
Naomi [import]uid: 67217 topic_id: 19903 reply_id: 129304[/import]
Joshua, i had a app rejected for this issue before i found your anwer in this thread:
[text]
Some people are getting their app’s rejected by Amazon because their supportedAndroidStores lists both “google” and “amazon”, but it turns out that Corona guessed wrong and launched the Google Play store instead. There is no nice way for Corona to guess correctly which store it belongs to if the app was installed by hand (in this case the app reviewer). So, I recommend that you do separate builds per app store that you are targeting and set the supportedAndroidStores to the appropriate store name. There isn’t really any other nice way of doing this… and it’s no different than what Java developers are doing who build with the Android SDK.
[/text]
Would it be possible for corona to control this by… hard coding this line of code:
[lua] supportedAndroidStores = { “google”, “samsung”, “amazon”, “nook” },[/lua]
When we build our app and have to select “Build For: Amazon/Kindle” from the menu.
It seems like you should know for a fact if we selected that option from the menu that this line of code could be… hard coded for us or over ridden… unless i am missing more of the puzzle. [import]uid: 88147 topic_id: 19903 reply_id: 129327[/import]
Hello,
I just got my app rejected for the first time due to the not using the Shop API (which I have not done on any of my previous apps). I am seeing how to link to individual apps, but I always have a “more games” button that links to all of my apps on the various stores. Is there a way to link to all of your apps using the Shop API?
Thanks,
Scott [import]uid: 79834 topic_id: 19903 reply_id: 129294[/import]
I just tried using this new API too, but it’s not working for me on iPod Touch. I wonder why. I’m currently using daily build 934.
Here’s the code I used (a very simple, plain vanilla, really):
local settings =
{
iOSAppID = "471409331",
}
native.showPopup("appStore", settings) I also tried this, but it didn’t work either (btw, I don’t have android version at the moment…):
local settings =
{
--requestView = "writeReview",
iOSAppID = "471409331",
nookAppEAN = " ",
androidAppPackageName = " ",
supportedAndroidStores = { "samsung", "google", "amazon", "nook" },
}
native.showPopup("appStore", settings) Here’s what works for me at the moment:
local id = "471409331"
local url = "https://itunes.apple.com/app/id" .. id .. "?mt=8"
system.openURL(url) All I want is to send the user to the app store so that he/she may consider downloading it.
What am I doing wrong?
Also, is it better to use native.showPopup over system.openURL? And if yes, why?
Naomi [import]uid: 67217 topic_id: 19903 reply_id: 129296[/import]
Hi Naomi,
I used this only for the Nook version and it passed testing:
local buyOptions =
{
nookAppEAN = “myOtherAppEAN”,
supportedAndroidStores = { “nook” },
}
native.showPopup(“appStore”, buyOptions)
For Amazon, iTunes and Google Play versions I have what you have, the https link.
I think the advantage might be that with this new API the page is in a box over/in your app and the user can press the x button to close the store page/box and he is still in your app.
With the https link the user goes to the store and is out of your app, she needs to quit the store and reopen the app to go back to it.
good luck. [import]uid: 32063 topic_id: 19903 reply_id: 129303[/import]
Thank you, Luciane! I appreciate you letting me know. I’ll keep using the system.openURL for Apple App Store, and use the new API for NOOk when it’s ready then.
Cheers,
Naomi [import]uid: 67217 topic_id: 19903 reply_id: 129304[/import]
Joshua, i had a app rejected for this issue before i found your anwer in this thread:
[text]
Some people are getting their app’s rejected by Amazon because their supportedAndroidStores lists both “google” and “amazon”, but it turns out that Corona guessed wrong and launched the Google Play store instead. There is no nice way for Corona to guess correctly which store it belongs to if the app was installed by hand (in this case the app reviewer). So, I recommend that you do separate builds per app store that you are targeting and set the supportedAndroidStores to the appropriate store name. There isn’t really any other nice way of doing this… and it’s no different than what Java developers are doing who build with the Android SDK.
[/text]
Would it be possible for corona to control this by… hard coding this line of code:
[lua] supportedAndroidStores = { “google”, “samsung”, “amazon”, “nook” },[/lua]
When we build our app and have to select “Build For: Amazon/Kindle” from the menu.
It seems like you should know for a fact if we selected that option from the menu that this line of code could be… hard coded for us or over ridden… unless i am missing more of the puzzle. [import]uid: 88147 topic_id: 19903 reply_id: 129327[/import]
Naomi,
You have a typo in your settings table. It needs to be [lua]iOSAppId[/lua] with a lower case ‘d’, not a capital ‘D’. That will make it work.
We spell it with a lower case ‘d’ because it is an abbreviation and not an acronym. [import]uid: 32256 topic_id: 19903 reply_id: 129387[/import]
team1,
Yes, we can change the code to make Amazon builds prefer the Amazon app store. However, there is no way to make this work between the Google Play and Samsung app stores… which is why I now tell people to change the [lua]supportedAndroidStores[/lua] setting to the one store you are supporting per build. There’s just no other nice way of handling this at the moment. Even Java developers that use the Android SDK have to do it this way. [import]uid: 32256 topic_id: 19903 reply_id: 129388[/import]
Naomi,
You have a typo in your settings table. It needs to be [lua]iOSAppId[/lua] with a lower case ‘d’, not a capital ‘D’. That will make it work.
We spell it with a lower case ‘d’ because it is an abbreviation and not an acronym. [import]uid: 32256 topic_id: 19903 reply_id: 129387[/import]
team1,
Yes, we can change the code to make Amazon builds prefer the Amazon app store. However, there is no way to make this work between the Google Play and Samsung app stores… which is why I now tell people to change the [lua]supportedAndroidStores[/lua] setting to the one store you are supporting per build. There’s just no other nice way of handling this at the moment. Even Java developers that use the Android SDK have to do it this way. [import]uid: 32256 topic_id: 19903 reply_id: 129388[/import]
@Joshua: Hey I hope you are doing good!
Quick question if I may: Is the popup window “smart”? What I mean by that is, if the user actually go a leave a review/rating, would the window stops showing from that point on? On the other end, if the user click on “ok” and get to the iTunes store and fail to leave a review/rating, would the system show the rating pop-up at later date? How much later (or how many app starts later)?
I realize you mostly work on the Android side but I am assuming the logic on both ios and android will work basically the same way.
Thanks a lot Josh.
Mo
@LairdGames
EDIT: I cannot for the life of me find the link to the “RateApp” API? [import]uid: 100814 topic_id: 19903 reply_id: 129503[/import]
Hey, Joshua, thank you for spotting the typo! I appreciate it.
Naomi [import]uid: 67217 topic_id: 19903 reply_id: 129534[/import]
@Joshua: Hey I hope you are doing good!
Quick question if I may: Is the popup window “smart”? What I mean by that is, if the user actually go a leave a review/rating, would the window stops showing from that point on? On the other end, if the user click on “ok” and get to the iTunes store and fail to leave a review/rating, would the system show the rating pop-up at later date? How much later (or how many app starts later)?
I realize you mostly work on the Android side but I am assuming the logic on both ios and android will work basically the same way.
Thanks a lot Josh.
Mo
@LairdGames
EDIT: I cannot for the life of me find the link to the “RateApp” API? [import]uid: 100814 topic_id: 19903 reply_id: 129503[/import]
LairdGames,
>> Is the popup window “smart”?
Nope. 
It merely shows the app details window in the app store. That’s it. You have to make it smart.
There is no way to know if the end-user has rated the app. Apple does not make that information accessible. Nor do we have any control of how the iTunes App Store manages the “Remind Me Later” alert. That’s just how Apple made it.
My advise is to do the following:
- Show a “Rate this App” option within your own app all of the time, like on the main screen.
- Bug the end-user with a native alert only once to rate your app. Perhaps after a couple hours since the first time they started the app.
To see documentation for this new feature, you have to download it from our daily build page. It’s part of the CoronaApiDocs zip file that you see listed there. The reason that you can’t find documentation of this feature on our website is because it is currently beta. All features we’ve added since the last release won’t be in our public documentation until our next release. ie: Our API documentation on our website only covers the release version of our software.
I hope this helps! [import]uid: 32256 topic_id: 19903 reply_id: 129559[/import]
Hey, Joshua, thank you for spotting the typo! I appreciate it.
Naomi [import]uid: 67217 topic_id: 19903 reply_id: 129534[/import]
LairdGames,
>> Is the popup window “smart”?
Nope.
It merely shows the app details window in the app store. That’s it. You have to make it smart.
There is no way to know if the end-user has rated the app. Apple does not make that information accessible. Nor do we have any control of how the iTunes App Store manages the “Remind Me Later” alert. That’s just how Apple made it.
My advise is to do the following:
- Show a “Rate this App” option within your own app all of the time, like on the main screen.
- Bug the end-user with a native alert only once to rate your app. Perhaps after a couple hours since the first time they started the app.
To see documentation for this new feature, you have to download it from our daily build page. It’s part of the CoronaApiDocs zip file that you see listed there. The reason that you can’t find documentation of this feature on our website is because it is currently beta. All features we’ve added since the last release won’t be in our public documentation until our next release. ie: Our API documentation on our website only covers the release version of our software.
I hope this helps! [import]uid: 32256 topic_id: 19903 reply_id: 129559[/import]
I am trying to set this up and have the same lag issue that was described in earlier posts. It takes about 20-40 seconds before a popup occurs with the store info. After about 4 seconds, I can tap the screen and the popup will appear then. Am I doing something wrong or is this really a Nook issue?
Thanks,
Scott [import]uid: 79834 topic_id: 19903 reply_id: 129863[/import]