native.showAlert on Nook?

Solar2D Android
#1

Can someone at CoronaLabs (or anyone else) confirm something…

I am getting repeated rejects from the Nook App Store due to a button in my game. It is an exit button, and when pressed I call native.ShowAlert() asking if the user wants to quit. Never had a problem with this code, works for everything other device I can test on (Apple, Droid phone). I do not have a Nook.

I am using Build 931. I opened a case to request more info from the Nook app testers as well.

An aside… I have submitted 7 times and each time there is a rejection based on something that was previously working since the beginning. BN testers sent me crash logs, rejected apps on button failures, etc, and this does not happen on any other platform!

I also have a live version that is throwing corruption errors all of a sudden when people install it and I cannot remove it or get an update to replace it.

I would greatly appreciate some help here. I have no idea what’s going on with my Nook submittal at this point. Seems like I also missed the October 15 deadline due to all of these issues. [import]uid: 114363 topic_id: 31957 reply_id: 331957[/import]

#2

We’ve tested native.showAlert() on a Nook HD and had no issues with it. So, what exactly was the problem?

You’re not calling [lua]os.exit()[/lua] when the end-user chooses to exit are you? If so, then that can get you rejected because that terminates your app in a not-so-nice way. It would appear as a crash in the Android log. If this is the case, then I recommend that you call [lua]native.requestExit()[/lua] instead, which exits the app gracefully. Just note that this function only works on Android and will do nothing on iOS or the Corona Simulator. [import]uid: 32256 topic_id: 31957 reply_id: 127512[/import]

#3

thanks for the reply Joshua…

Nope, not calling [lua]os.exit()[/lua]. I am actually checking for a “yes” button click and then I am calling [lua]storyboard.gotoScene()[/lua] to leave the game screen and go back to the title screen.

I asked BN what’s is happening but by the description of the last reject email, they are saying that nothing happens when the “back” button is touched.

Frustrating to be sure… All other platforms works as it should and since that button was always in the game, it must of worked previously as well.

The Nook is my highest generating platform and I am having nothing but problems with this submitted, as well as the current live version (literally live for months and now throws errors). I am not sure what’s going on… But if both a new submittal and live app are not working properly, I am beginning to wonder if there was some sort of nook update that is causing problems with some apps???

Lets see what BN says about the alert pop up. I am disappointed that I missed the 10/15 deadline for submittal and the ongoing issues with my live version… Starting to panic a bit, actually. [import]uid: 114363 topic_id: 31957 reply_id: 127526[/import]

#4

I know we’ve tested overriding key events on the Nook HD too. I’m a bit baffled as to what might be wrong as well. Hopefully B&N’s response will provide more clues. [import]uid: 32256 topic_id: 31957 reply_id: 127532[/import]

#5

We’ve tested native.showAlert() on a Nook HD and had no issues with it. So, what exactly was the problem?

You’re not calling [lua]os.exit()[/lua] when the end-user chooses to exit are you? If so, then that can get you rejected because that terminates your app in a not-so-nice way. It would appear as a crash in the Android log. If this is the case, then I recommend that you call [lua]native.requestExit()[/lua] instead, which exits the app gracefully. Just note that this function only works on Android and will do nothing on iOS or the Corona Simulator. [import]uid: 32256 topic_id: 31957 reply_id: 127512[/import]

#6

thanks for the reply Joshua…

Nope, not calling [lua]os.exit()[/lua]. I am actually checking for a “yes” button click and then I am calling [lua]storyboard.gotoScene()[/lua] to leave the game screen and go back to the title screen.

I asked BN what’s is happening but by the description of the last reject email, they are saying that nothing happens when the “back” button is touched.

Frustrating to be sure… All other platforms works as it should and since that button was always in the game, it must of worked previously as well.

The Nook is my highest generating platform and I am having nothing but problems with this submitted, as well as the current live version (literally live for months and now throws errors). I am not sure what’s going on… But if both a new submittal and live app are not working properly, I am beginning to wonder if there was some sort of nook update that is causing problems with some apps???

Lets see what BN says about the alert pop up. I am disappointed that I missed the 10/15 deadline for submittal and the ongoing issues with my live version… Starting to panic a bit, actually. [import]uid: 114363 topic_id: 31957 reply_id: 127526[/import]

#7

I know we’ve tested overriding key events on the Nook HD too. I’m a bit baffled as to what might be wrong as well. Hopefully B&N’s response will provide more clues. [import]uid: 32256 topic_id: 31957 reply_id: 127532[/import]