app signing

It isn't really that hard. There are already some threads on it, search for them.

Check the help file in MMF.
I followed it and had never signed an app before and it was pretty easy to do.

Well, this has been very frustrating.

I spent several hours today on this and I can tell you that it is definitely NOT easy. It's because too many things can go wrong. Generating the keystore is easy enough, but I cannot get the app signed because of an SHA1 error... I read online that it could be a conflict between java 1.6 and java 1.7, but I downloaded 1.7 anyway because I saw in the instructions that it's working, but was the entire process checked?

What I didn't realize until just NOW is that MMF2 has a "release mode" button that needs to be checked.. I was using the output file as what I assumed was an unsigned app, but now I see that there is a place for a keystore? So confused.

However, from the help file, I don't know what this does exactly. Does it sign the app? Does it verify it? Is it zip aligned when you finish or is that an additional step you need to do by yourself?

So, yes, there probably should be a tutorial because a ton of people are going to be asking about this. I would be happy to do it myself, but I haven't been able to get it working yet.

What are we supposed to do exactly with the apk file that MMF2 spits out?

it's true, it's not very hard. but like the other day i forgot that the alias is the key name too.

but I miss-read the instructions. Just have a careful reading of the instructions, now that I look at them I am like... it's like so clear what to
do. But again when you are doing something for the first time it seems harder than what is actually is.

Release mode signs it, zip-aligns it and the final APK output is ready for release onto any store (Google, Amazon) etc.

Okay, thanks Sparckman and Danny. I did eventually get it on the OUYA and I was shocked that it worked with the OUYA mouse with no problems because I'm using a bunch of qualifiers.

I'm guessing that if you don't check "release mode" MMF2 exports the apk as a signed app in debug mode, but I could be wrong. This would have prevented me from signing it manually through the command line. Since we have to generate the keystore, I didn't realize that was the only part of the signing process that had to be done manually.

So, I will be writing a tutorial today because I'm probably going to forget, but this will also save people a lot of headaches in the future.

Quote from redpandagames

Okay, thanks Sparckman and Danny. I did eventually get it on the OUYA and I was shocked that it worked with the OUYA mouse with no problems because I'm using a bunch of qualifiers.

I'm guessing that if you don't check "release mode" MMF2 exports the apk as a signed app in debug mode, but I could be wrong. This would have prevented me from signing it manually through the command line. Since we have to generate the keystore, I didn't realize that was the only part of the signing process that had to be done manually.

So, I will be writing a tutorial today because I'm probably going to forget, but this will also save people a lot of headaches in the future.

Well, a tutorial will be nice, but be sure to mention Please login to see this link., since it works great from what I've heard.

I actually made a tutorial for this, and made note of it in another forum post: Please login to see this link.