thanks for the help, but the message I received is not about ascii armor format, but about the fact the key seems invalid...
I can generate the ascii armor format error if I change the encoding of the key txt file let's say from ANSI to UTF-8, but this is a different matter (I think)
Also, I uploaded my key to the MIT gpg public server. Also their app requires a full ascii armor format, but there my key was uploaded and verified without no problem.
If you want, you can check my key at http://pgp.mit.edu/pks/lookup?op=get&search=0xABF9A0C376B5D965