B&N Nook HD App Rejections

I’ve had 6 apps rejected for B&N’s Nook HD. All of their responses are either “DRM” or “Does not work on ICS”. Neither of these errors is helpful in the slightest, and I’ve gotten no response from their support.

I saw in a recent blog post others were having similar problems and Corona was working with them to resolve issue. Are there any updates on this? [import]uid: 84258 topic_id: 31547 reply_id: 331547[/import]

Corona SDK Daily Builds
CoronaSDK 2012.925
Post date:
Fri, 2012-09-28 21:33
Release notes for build 2012.924 through 2012.925

Android: Added Nook HD/HD+ support.
Android: Maintenance
Cases affected:

Project release files:
CoronaSDK-2012.925.msi
CoronaSDK-2012.925.dmg
CoronaApiDocs-2012.925.zip

Source: http://developer.coronalabs.com/release/2012/925/
[import]uid: 89165 topic_id: 31547 reply_id: 126030[/import]

Thank for the information and the update to the Daily Build.

Just one question.

With this daily build is “everything” else within the build is going to be pretty “safe”. I mean the way I understand it, the Daily Builds are a “work in progress”. Just because this gives us the support we need for Nook HD/HD+ ,is everything else going to continue to work?

Sorry for the concern, but there is a big deadline riding on this update submission with Barnes & Noble.

Thanks
Rob
[import]uid: 16527 topic_id: 31547 reply_id: 126049[/import]

Hi guys - we are in the middle of testing stuff for the new Nooks. More info coming soon. [import]uid: 10668 topic_id: 31547 reply_id: 126050[/import]

I like to think of Daily Builds as living on the bleeding edge. For the most part, daily builds are “reasonably stable”. Corona Labs does a pretty good job of unit testing the things they are releasing and I’ve had pretty good luck with dailies, only having had to roll back a couple of times. I’m feature driven. For instance when iOS 6 stopped showing print statements in device console logs and I’m doing things that need tested on devices (and the only feed back I can get from testers is console logs), there was no choice but to get the daily build that fixed the problem.

Given that bugs get fixed and new features added, I feel that staying up-to-date is important.

Now flip the coin. I have a couple of apps that use tableView’s that were built way back in the 720’s build number wise and I’ve not had to touch them. With today’s version (stable or not), I’m probably going to have to update the code to modernize it with today’s variant of tableView… But in this case I have to do it or my may not work with new devices.

In this case, if B&N can’t work out this DRM issue on their side and Corona Labs has to change something for us to submit apps, then you won’t have a choice but to upgrade. Now Coronal Labs did set a precedent with the retina iPad by going back to a previous stable build and updating it. But it was a pain in the butt on our part to deal with different versions of build 704. I can only imagine how much of a headache it was on their staff to have to maintain the code.
[import]uid: 19626 topic_id: 31547 reply_id: 126080[/import]

Hi guys - quick update on the Nook HD, please take a look here:
http://www.coronalabs.com/blog/2012/10/01/corona-update-on-nook-hd [import]uid: 10668 topic_id: 31547 reply_id: 126116[/import]

Corona SDK Daily Builds
CoronaSDK 2012.925
Post date:
Fri, 2012-09-28 21:33
Release notes for build 2012.924 through 2012.925

Android: Added Nook HD/HD+ support.
Android: Maintenance
Cases affected:

Project release files:
CoronaSDK-2012.925.msi
CoronaSDK-2012.925.dmg
CoronaApiDocs-2012.925.zip

Source: http://developer.coronalabs.com/release/2012/925/
[import]uid: 89165 topic_id: 31547 reply_id: 126030[/import]

Thank for the information and the update to the Daily Build.

Just one question.

With this daily build is “everything” else within the build is going to be pretty “safe”. I mean the way I understand it, the Daily Builds are a “work in progress”. Just because this gives us the support we need for Nook HD/HD+ ,is everything else going to continue to work?

Sorry for the concern, but there is a big deadline riding on this update submission with Barnes & Noble.

Thanks
Rob
[import]uid: 16527 topic_id: 31547 reply_id: 126049[/import]

Hi guys - we are in the middle of testing stuff for the new Nooks. More info coming soon. [import]uid: 10668 topic_id: 31547 reply_id: 126050[/import]

I like to think of Daily Builds as living on the bleeding edge. For the most part, daily builds are “reasonably stable”. Corona Labs does a pretty good job of unit testing the things they are releasing and I’ve had pretty good luck with dailies, only having had to roll back a couple of times. I’m feature driven. For instance when iOS 6 stopped showing print statements in device console logs and I’m doing things that need tested on devices (and the only feed back I can get from testers is console logs), there was no choice but to get the daily build that fixed the problem.

Given that bugs get fixed and new features added, I feel that staying up-to-date is important.

Now flip the coin. I have a couple of apps that use tableView’s that were built way back in the 720’s build number wise and I’ve not had to touch them. With today’s version (stable or not), I’m probably going to have to update the code to modernize it with today’s variant of tableView… But in this case I have to do it or my may not work with new devices.

In this case, if B&N can’t work out this DRM issue on their side and Corona Labs has to change something for us to submit apps, then you won’t have a choice but to upgrade. Now Coronal Labs did set a precedent with the retina iPad by going back to a previous stable build and updating it. But it was a pain in the butt on our part to deal with different versions of build 704. I can only imagine how much of a headache it was on their staff to have to maintain the code.
[import]uid: 19626 topic_id: 31547 reply_id: 126080[/import]

Hi guys - quick update on the Nook HD, please take a look here:
http://www.coronalabs.com/blog/2012/10/01/corona-update-on-nook-hd [import]uid: 10668 topic_id: 31547 reply_id: 126116[/import]