3
All tutorials point to a single path, when generating the SHA1 or MD5 sequence to be used in Google Console, in order to get the Key API to be put in the manifest.xml file.
I mean, they say go to the prompt command and enter that long sequence of
keytool -list -alias [apelido] -keystore [nome do arquivo keystore] -keypass [senha]
that will return MD5 or SHA1, depending on whether you use -v or not as another key in the above command.
However, I noticed that the SHA1 generated by the command is the same one that is obtained when APK is generated, through the Eclipse menu action (Export, project, key, apk name). The last window, when Eclipse compiles the application displays the same characters.
My question: instead of typing through the Windows dos prompt, it’s no longer practical to compile the application, copy the SHA1, take it to Google Console, paste it in with the application package, take the generated Key API, back to the application and edit the manifest.xml tag and recompile to enforce map usage?
Friends, I have found the answer, very good: http://stackoverflow.com/questions/6528691/fragments-in-android-2-2-2-2-2-0-is-this-possible
– user4701
This comment belongs to another question you posted: http://answall.com/questions/4488/comort-makefunction-maps-em-apis-antigas-e-novas-ao-mesmo-tempo
– Piovezan
Put the solution here as a response and accept it. You help other people and can still gain reputation.
– Maniero
Dear Piovezan, I walk so stunned in this programming with Android, because I am self-taught, that I am confusing the posts.
– user4701
Dear bigown, I stop doing things even for my own benefit because I ignore (sometimes I can’t understand the various awards, advantages, disadvantages - it’s a lot!) and I still have time to update. I am running against the clock. You commented for me to put the solution as an answer and accept, I did not quite understand what you meant.
– user4701