![]() ![]() This signature is used to verify authenticity. That’s a really cool one liner, but what you need to know is that it generates a file (called a “keystore”) that can be used to “sign” an Android application. Manages a keystore (database) of cryptographic keys, X.509 certificate chains, and trusted certificates. My first result is Oracle’s documentation saying: Whenever I need to figure out what a command does, I search for man. Currently Firebase Dynamic Links and some Firebase Authentication products (such as Google Authentication and Phone Authentication) are the only products that need a SHA-1. This is also an optional step for many of Firebase’s products. 'keytool' is not recognized as an internal or external command Others will get one of these super exciting error messages: Now for many developers, including most Google employees with the standard dev tools, this just works and we don’t question it. If you’ve followed any of the Firebase tutorials for Android, you probably came across an instruction like “Add the SHA-1 hash for your project.” You may have even been linked to this page, where you were told to type keytool -list -v followed by a strange symbols involving -keystore. ![]() What’s keytool, why can’t it be found, and why does Firebase even want a “SHA-1”? ![]()
0 Comments
Leave a Reply. |