Video-keystore and publishing problem solutions

The_Gamesalad_Guru

I show you how to fix the publishing problems.
Link to keystore video: http://forums.gamesalad.com/discussion/34634/publishing-to-android-a-step-by-step-guide#Item_31

The_Gamesalad_Guru

One other note, the build that I did in the video was an iphone project not a kindle project. I took an iphone project and selected publish and then selected Android as my target platform. I'm going to try doing it as a kindle project and see what happens. I'm trying to help..lol

The_Gamesalad_Guru

I saw that in the Android 3.2 3.1 and another
section you didn't have the Google API's by Google installed. I have that installed

The_Gamesalad_Guru

I'm just looking for diferences between you and I

The_Gamesalad_Guru

I have to believe if we can mirror my settings you will be able to publish, I can't image how the server could let me publish and not you. Plus I did get the same error as you are and this is how I fixed it.

Jel

Guys just my two cents but I've been using Eclipse and Photics instructions below for getting my keystore's and they have all worked so far without any problems.

Photics:
October 5, 2009 at 4:13 PM
I’ve been checking my web traffic report. Apparently, this article is popular. Although, you might want to know that the process is much easier for me now.
Step #1 – In Eclipse, Right-Click my project
Step #2 – Select Android Tools > Export Signed Application Package.
Then, I just follow the prompts.
It’s a lot easier with a graphical user interface!

The_Gamesalad_Guru

Also I deleted my old key before I made a new one. Because in the second window of the verify password is says mykey just like in Arrons video. I noticed yours had the key name which means it's seeing other keys. I would delete all the keys and them make a new one.

butterbean

I'm also unable to publish, I even trashed the old key, and created a completely new one, and still get the same error.

The_Gamesalad_Guru

OKay so I made another key and have two. I noticed the second box still said MYKEY and not the key name like yours did. Yours said tshirtboothgame even with two keys in the same spot mine still limited me to MYKEY. Why is that different?

butterbean

His said Tshirtboothgame because he named it that when he generated the key right? Isn't the name whatever you name your key in the terminal?

The_Gamesalad_Guru

I'm about to post a video to show him. Even with three keys it still says mykey

The_Gamesalad_Guru

butterbean

WOW... .I'm finally able to publish! turns out the issue all along for me was that I dragged the icon into the image box instead of manually selecting it from the folder!!

Craziness!!!

The_Gamesalad_Guru

Like I said it's alway some little thing!

ultima

looks like it's solved.

Rob2

Just remember...

You only ever need to create ONE keystore file which will contain ONE key pair (private and public) and this you will use to sign ALL your Android releases.

beefy_clyro

That sounds pretty straightforward @Rob2 but let me get this right;

I have created a keystore for Android, i have managed to publish a android project, got it back as signed and unsigned and have managed to install on my Fire. So, on my next build, i can use the same keystore as i did for the 1st game?

Rob2

That is the recommended method

FallacyStudios

...............................Seriously.......... the error the whole time was dragging and dropping???? Side question... Could that be the reason my other app was rejected by Apple was because I drag and dropped the icon and when they reviewed it my icons didn't match?

beefy_clyro

Awesome, cheers.

@FallacyStudios ... No, Apple icon dragging is fine, its just with Android its not. If you are rejected by Apple from having icons that aren't the same then that is why they have rejected you. The one you put in iTunes connect and the one you put in GS when publishing must be the same (or very very minor differences).

FallacyStudios

@beefy_clyro Nah I'm pretty positive it was the same icon. The screenshots they sent me was one was the one I put up that was the correct one. And the other is that blue default GS icon. And I do remember dragging and dropping the one I put up on the market into the box during publishing. Just though maybe the drag and drop was the issue. When I go back to look at the app in the publish update section the icon does show the blue default where as when I find it by browsing on my other apps I just put up on Android it does display the actual icon. I figured it was a fluke. But if it comes back again rejected for that reason I'll do the browse way cause I'm still thinking that may have been my problem.