LINT errors warnings in Eclipse. Keeping me from getting my SHA1 signature. Get your sha1 and md5 thumbprint for debug keystore (also works for your other keystores). Go to you package exporter in Eclipse (defaults to the left side) right click it>android tools>export signed application package AndroidManifestxml:60 Avoid hardcoding the debug mode; leaving it out allows debug and release builds to automatically assign one Issue: Checks for hardcoded values of android:debuggable in the manifest Id: HardcodedDebugMode It's best to leave out the android:debuggable attribute from the manifest. If you do, then the tools will automatically insert android:debuggable=true when building an APK to debug on an emulator or device. And when you perform a release build, such as Exporting APK, it will automatically set it to false. If on the other hand you specify a specific value in the manifest file, then the tools will always use it. This can lead to accidentally publishing your app with debug information. auth_strings.xml:4 "auth_client_using_bad_version_title" is translated here but not found in default locale Issue: Checks for translations that appear to be unused (no default language string) Id: ExtraTranslation If a string appears in a specific language translation file, but there is no corresponding string in the default locale, then this string is probably unused. (It's technically possible that your application is only intended to run in a specific locale, but it's still a good idea to provide a fallback.). Note that these strings can lead to crashes if the string is looked up on any locale not providing a translation, so it's important to clean them up. [] common_strings.xml:5 "common_google_play_services_notification_ticker" is not translated in be Issue: Checks for incomplete translations where not all strings are translated Id: MissingTranslation If an application has more than one locale, then all the strings declared in one language should also be translated in all other languages. If the string should not be translated, you can add the attribute translatable="false" on the <string> element, or you can define all your non-translatable strings in a resource file called donottranslate.xml. Or, you can ignore the issue with a tools:ignore="MissingTranslation" attribute. By default this detector allows regions of a language to just provide a subset of the strings and fall back to the standard language strings. You can require all regions to provide a full translation by setting the environment variable ANDROID_LINT_COMPLETE_REGIONS. You can tell lint (and other tools) which language is the default language in your res/values/ folder by specifying tools:locale="languageCode" for the root <resources> element in your resource file. (The tools prefix refers to the namespace declaration http://schemas.android.com/tools.) []

You can just delete that out of your manifest.(debuggable statement) Clean your app and both of those errors should go away.

OK, I did it! I just had my first full-fledged success with my Android App (4:30pm PDT 2014-06-06)... but I did 3-4 things to get there, including this. And Right Click > Android Properties > Fix Project Properties And Q)uit Eclipse, Clean, and restart twice. Redid my Google API key. Somewhere in that VooDoo dance, IT WORKS!