[NOOK] Walkthru - Deploying on a Test Device and Getting Ready for Store Deployment

Getting Started Newbie Questions
#21

Wow, very thorough. I’m sure many others will benefit from this.

Anyhow, a quick note based on my experience:

  1. I did install Samples for SDK when I first installed Android SDK. Then later on (and it was after I successfully installed on Nook), I thought these samples are probably not necessary, so I uninstalled them (using Android SDK Manager). Even after I uninstalled the samples, I am still able to install my apk on Nook, so it could be that installing Samples for SDK isn’t necessary. (Keep in mind, I did install once and then uninstalled them – but I don’t see why installing and uninstalling would make any difference to not installing at all.)

  2. When I install Nook build, I place it in platform-tools (just like Gregory). However, I don’t go through kill-server and start-server bit. I wonder why Gregory needs to do it. My Macbook is not hooked to any backend server, and I use it just like anyone would use a laptop on the run. Is Gregory using some sort of corporate-network-server connected Mac or something?

  3. Once I change the terminal directory to platform-tools directory, all I do is to type in the install command. That’s it. Pretty streamlined. i.e., Launch terminal, change directory to platform-tools, type install command. Nothing else.

  4. Good to know how to search for the app – I was using another method to find it, which is:

  1. Home button ( the n )
  2. Apps menu (bottom menus )
  3. Then click on the volume notification button (+) until it’s in its fullest, and WHILE HOLDING IT
  4. Tap on the top left corner of the device ( where library is )
    (from http://developer.anscamobile.com/forum/2011/11/28/nook-builds#comment-94598)

Cheers,
Naomi [import]uid: 67217 topic_id: 24855 reply_id: 102314[/import]

#22

Naiomi is most likely right on those 3 points above. You may not need to install the Android SDK Sample files, it was selected by default, so I installed it. 2. Not sure why I had to kill Servers, but it worked, it’s an extra 10 second step that might keep you from having unexpected problems. Thanks everyone for your participation. Hope this helps you all like it helped me. [import]uid: 90878 topic_id: 24855 reply_id: 102915[/import]

#23

Has anyone gotten this working under 64-bit Windows 7?

I’ve followed all of the steps outlined above and other other websites, but although I can see my Nook via the PC drivers, I do not see it if I type in:

adb devices

The only thing I can find is some comments about Windows 7 being agressive about using its drivers rather than the Google USB driver. I saw this on the Nook Dev site:

Windows7 is super aggressive with auto-associating drivers.  
  
You have to go into the system settings (Right Click on My Computer -\> Properties -\> Advanced System Settings - \>Hardware  
  
Then click on Device Installation Settings and tell it 'No, Let me choose what to do'  
  
Then go back into device manager, yank out the mass storage device, unmount/remount the device and you should get into a state where the device manager now has an 'other device' with Nook Color under that heading.

Tried that, but still appears to be using the Windows USB driver.

So, has anyone gotten this working under 64-bit Windows 7?

[import]uid: 16734 topic_id: 24855 reply_id: 103945[/import]

#24

I’m in the UK, so blissful in my ignorance when it comes to testing on Fire and Nook. B & N must be desperate for content, having at last finally opened their doors to foreign submissions.

I’ve been accepted, so I’ll have a go at trying to send something off blind. It’s working on the Corona Nook simulator anyway! So, if I’m not testing on a device what are the steps?

If I get a keystore and certificate to put in the Corona build would that be enough to create the .apk to send off to Nook?

Many thanks… [import]uid: 94653 topic_id: 24855 reply_id: 106667[/import]

#25

Yeah, that should be ok, but I HIGHLY recommend that you test on a device before sending it off to NOOK. If you want to try to find me on the IRC Room (known as Tyraziel on #Corona on freenode.net) I might be able to load the APK on my device to some quick testing. [import]uid: 57050 topic_id: 24855 reply_id: 106955[/import]

#26

@Ken – Unfortunately I don’t have a windows 7 64 bit machine so I can’t help you out here. [import]uid: 57050 topic_id: 24855 reply_id: 106956[/import]

#27

Thanks for the offer of help. I’ve had a Nook app rejected because the record audio was making the app crash. There’s some feedback from Nook via the link below. Do you spot anything?

http://developer.anscamobile.com/forum/2012/05/30/nook-reject-because-record-audio

[import]uid: 94653 topic_id: 24855 reply_id: 109952[/import]

#28

In case this helps anyone - no adb command in the Terminal was working for me on my Mac.
Not “adb devices” or “adb kill-server” or “adb start-server”

I had to type this in (found it on another site):

$ export PATH=$PATH:/Users/YOUR-USERNAME/Desktop/android-sdk-macosx/platform-tools

After I did that, the adb commands would work.

Make sure to change the line after $PATH: to give the proper directory where you have your android platform-tools [import]uid: 42083 topic_id: 24855 reply_id: 111260[/import]

#29

The issue I am having is that when I try to use the Corona Simulator to “Build for Nook” it gives me the error of “Please enter a valid package name” no matter what I type in the field for “Package:”

Any ideas what I could do to be able to build an .apk to install on my Nook?

Thanks so much! [import]uid: 42083 topic_id: 24855 reply_id: 111262[/import]

#30

Valid Package Name a reverse domain style name. Something like:

com.mycompany.myapp [import]uid: 16734 topic_id: 24855 reply_id: 111267[/import]

#31

Thanks @KenRogoway, I tried com.mycompany.myapp (with my actual company name and the app’s name) and com.company.game.appName and just the app name and at least 20 other combinations but it still says to “Please enter a valid package name”…

I just tried “Build for Android” and “Build for Amazon/Kindle” and I get the same error on those as well.

I can build for iOS without a problem because there is no “Package:” field, I just select the app’s code signing identity from the drop down menu. [import]uid: 42083 topic_id: 24855 reply_id: 111271[/import]

#32

Great post!
I can’t see my nook color on my mac NOR my win7 pc.
I have installed android SDK, eclipse, and the plugins on both machines.
I have created the provision profile, uploaded to my nook root.
Yet, nothing.
any clues?
thanks
EDIT: got it to work!!!

I followed this tutorial on nook developers (I think you need to have a developer account to see it)
https://nookdeveloper.zendesk.com/entries/21153112-making-nook-work-with-adb-and-windows-7-every-time

cheers!!!
[import]uid: 12407 topic_id: 24855 reply_id: 112695[/import]

#33

I’ve heard getting adb to work correctly on windows 7 can be tricky… (I don’t have a win7 machine so I couldn’t go through the additional pain…) thanks for posting this. I’ll add it to my main post.

Edit:
I guess I can not edit my original post… [import]uid: 57050 topic_id: 24855 reply_id: 112733[/import]

#34

We have one app on the Nook store.
Our second app is being rejected by Nook with the error message below.
This app was accepted to the appstore, google play and amazon first time without problems. The keystore for Android was created using keytool.
The apk I submit is called “Meet Pickles.apk” (same as for the android and amazon builds)
I’ve submitted different builds built with different corona versions but they all get rejected with the same message.
Anyone had this problem before? Any ideas?

Whoops: didn’t find expected signature
read_central_directory_entry failed
file ‘MeetPicklestheHamster-15196-application-2.apk’ is not a valid zip file
rm failed for /data/local/tmp/MeetPicklestheHamster-15196-application-2.apk, No such file or directory

Error from jarsigner when checking for the signature:
jarsigner: java.util.zip.ZipException: invalid LOC header (bad signature) [import]uid: 32063 topic_id: 24855 reply_id: 123693[/import]

#35

We have one app on the Nook store.
Our second app is being rejected by Nook with the error message below.
This app was accepted to the appstore, google play and amazon first time without problems. The keystore for Android was created using keytool.
The apk I submit is called “Meet Pickles.apk” (same as for the android and amazon builds)
I’ve submitted different builds built with different corona versions but they all get rejected with the same message.
Anyone had this problem before? Any ideas?

Whoops: didn’t find expected signature
read_central_directory_entry failed
file ‘MeetPicklestheHamster-15196-application-2.apk’ is not a valid zip file
rm failed for /data/local/tmp/MeetPicklestheHamster-15196-application-2.apk, No such file or directory

Error from jarsigner when checking for the signature:
jarsigner: java.util.zip.ZipException: invalid LOC header (bad signature) [import]uid: 32063 topic_id: 24855 reply_id: 123693[/import]

#36

@Luciane – We talked briefly on IRC, did you end up resolving your problem? [import]uid: 57050 topic_id: 24855 reply_id: 126725[/import]

#37

TozSoftware – yes and no. Nook support found out it is a error in their system (!!!). Two of their people downloaded the same apk directly from a link I provided bypassing their system, installed and all worked no problem. They are still fixing their system and therefore my app hasn’t been approved yet. [import]uid: 32063 topic_id: 24855 reply_id: 126729[/import]

#38

@Luciane – Glad to see that the problem wasn’t on your end! Hopefully they fix it soon so you can get your app out there! [import]uid: 57050 topic_id: 24855 reply_id: 126737[/import]

#39

@Luciane – We talked briefly on IRC, did you end up resolving your problem? [import]uid: 57050 topic_id: 24855 reply_id: 126725[/import]

#40

TozSoftware – yes and no. Nook support found out it is a error in their system (!!!). Two of their people downloaded the same apk directly from a link I provided bypassing their system, installed and all worked no problem. They are still fixing their system and therefore my app hasn’t been approved yet. [import]uid: 32063 topic_id: 24855 reply_id: 126729[/import]