Hi, I submitted an app (Android) to the Amazon App Marketplace. They put it on hold because additional steps need to be taken before approval because I've got a share with Facebook option in the app. The easiest option is to remove the share option, but I don't want to do that. The other option is to submit an UNsigned .apk file. The process is this: I upload an unsigned .apk file (no problem) They wrap additional code around the file (no problem) I download the modified .apk file (no problem) I get this modified file signed (PROBLEM) I submit the modified and signed .apk file My question is, how do I get this modified .apk file signed? I thought I could just go through the eclipse export wizard and point in the relevent place to the modified .apk file, but that doesn't work, it comes up with an error missing signature. I've spent a day googling and visiting dev forums and Amazon documentation, but to no avail. Can anyone help please? You would think the natural course would be to contact Amazon support (I use the term loosely) but they're as useful as a chocolate teapot. Their reply (after 2 days) to my query above was: You must ensure that the binary is signed before submitting. Yeah, well, thanks for that...

I can think of lots of uses for a Chocolate Teapot. Hmm, this is perplexing. I don't have any experience with the Amazon process but will take this shot. Could it be that you also have Share via Twitter enabled, and not just Facebook? I say this because the Facebook code in your downloaded project is plain-jain .java source that you are compiling with the rest of you code. However, the Twitter code is embedded in a .jar file. Look under your project root, you'll see a jtwitter.jar file. The jtwitter component was not coded by us, it's an open-source twitter client that is easily included in Android projects. I wonder if it's the issue? Again, grasping here, have no idea. Does the Amazon message really only say 'additional steps are needed because Facebook is in the app' or do they provide more details? Not sure how to advise here.

It seems that twitter is ok, but not facebook. Here's the email. The steps are what I outlined in my OP. When we process your app to allow distribution through our Amazon Appstore, our technology over-writes your private signature with Amazon's. Since your application uses Facebook integration, we require that you do one of the following things: · Sign your apk following the steps below or · Remove the Facebook integration from your application If you opt to sign your apk and have a Live version already on our store, be aware that users will be forced to re-install your application as a new application, losing any saved data associated with any previous versions. We have placed your app(s) to a “Pending Action” status so that you can either remove Facebook as a feature or sign your binary, whichever you choose. If you've chosen to sign your apk, here are the instructions you need to follow: 1. Log in to the Developer Portal 2. Find the app you want to sign on the “My Apps” page and click “Edit app details” 3. From the Application Details page under the Upload Binary section, click “Edit” 4. If you already have a binary uploaded, click the “Remove” button 5. Make your DRM selection and click “No, I will sign my binary” 6. Upload your unsigned binary (on Developer Portal screen as “Step 1”) 7. Download the processed binary (on Developer Portal screen as “Step 2”) 8. Sign the binary downloaded on “Step 2” 9. Upload the newly signed binary to the portal (on Developer Portal screen as “Step 3”) 10. Click the Submit button.

Just like you described. You say PROBLEM when you sign their customized .apk. Do you get any errors in Eclipse? Maybe it's an Eclipse plug-in Export type issue. You can sign projects with the command line too (been a few years!) to bypass Eclipse if you think thats the trouble. This is screwy. If you look here: http://developer.android.com/guide/publishing/app-signing.html (i'm sure you already have) there is a section (#3) that describes signing with the command line. Who knows...could work. Amazon's killin devs lately with their new announcement yesterday about booting all their California affiliates..ugh

Hi, I'm having the same problem. I submitted a help request to Amazon on Monday and I have not heard back from them. I'm searching the web for an answer but turning up nothing. I don't have facebook or twitter, just maps. I'm ready to give up on amazon. Can I open the apk I downloaded from amazon with eclispe? I can't figure out how to sign the apk I download from them.

Problem Solved! Not really, I just removed the share on Facebook feature and added a big share button to a custom url. I suspect the solution is as David says and via the command line using keytool and jarsigner. Whatever the solution turns out to be, I don't think it's straightforward. ...I feel defeated...

Has somebody compiled with keytool and jarsigner to see if it worked as the Android docs say?

WOW!!!!!! It took over a week to hear from Amazon on this question but here's the email response I just got (below). I'm working on getting another project out the door so I may not try this for a couple of days. I want to share in case others are having problems or want to add to the reply. From Amazon: For more information on how to sign your app, please refer to this document: http://developer.android.com/guide/publishing/app-signing.html Please download the wrapped version from STEP 2 and double check to make sure that you are signing the wrapped version. The easiest way to tell is to unzip the files (rename the apk to .zip) and look for a file with a name similar to 'com.amazon.content.id.' If this file does not exist in the zip, it is NOT the wrapped version. Before you sign, please make sure that this .id file exist within the apk that you’re about to sign. Once you’ve signed the wrapped version, try uploading again into STEP 3. Using the signing tool in Eclipse that comes along with Android SDK plugin may remove the file mentioned above from the final package. Please try defaulting to jarsigner from Java JDK in commandline.

Finally got back to this project. Here's a simple way to sign a app. I just submitted app to the Amazon appstore. I will keep you posted. First, generate keystore: keytool -genkey -v -keystore key.keystore -alias my_alias -keyalg RSA -keysize 2048 -validity 10000 Choose your alias and keystore file, answer the questions and remember password. Second, sign your apk: jarsigner -verbose -keystore key.keystore my_application.apk my_alias You need the keystore file, alias and password from the keytool command. my_application.apk have to be unsigned. Please share your results.

@tiger - Thanks. This worked perfectly. Now just awaiting final approval from Amazon.

Yes, I'm having same issues as I have Google Maps. I'll have to figure out how to upload unsigned apk file just to re-download it again! Errrgghhh!