Android debug.keystore SHA1 是否对所有人都相同？
Does Android debug.keystore SHA1 is same for all?
debug.keystore 是在我们安装 android sdk 时自动生成的。那么我们的 debug.keystore 是否会在所有机器上使用相同的 SHA1？
每个人都不一样。对于特定系统，它会相同。
每台机器的调试密钥不会相同。而且你不会有相同的机器调试密钥，因为有 an expiry for the debug key:
The self-signed certificate used to sign your APK for debugging has an
expiration date of 365 days from its creation date. When the
certificate expires, you will get a build error.
To fix this problem, simply delete the debug.keystore file. The file
is stored in the following locations:
- ~/.android/ on OS X and Linux
- C:\Documents and
Settings\.android\ on Windows XP
- C:\Users\.android\ on
Windows Vista and Windows 7, 8, and 10
The next time you build and run
the debug build type, the build tools will regenerate a new keystore
and debug key. Note that you must run your app, building alone does
not regenerate the keystore and debug key.
您可能会在到期日期之前获得相同的调试密钥，但不要依赖它。
debug.keystore 是在我们安装 android sdk 时自动生成的。那么我们的 debug.keystore 是否会在所有机器上使用相同的 SHA1？
每个人都不一样。对于特定系统，它会相同。
每台机器的调试密钥不会相同。而且你不会有相同的机器调试密钥，因为有 an expiry for the debug key:
The self-signed certificate used to sign your APK for debugging has an expiration date of 365 days from its creation date. When the certificate expires, you will get a build error.
To fix this problem, simply delete the debug.keystore file. The file is stored in the following locations:
- ~/.android/ on OS X and Linux
- C:\Documents and Settings\.android\ on Windows XP
- C:\Users\.android\ on Windows Vista and Windows 7, 8, and 10
The next time you build and run the debug build type, the build tools will regenerate a new keystore and debug key. Note that you must run your app, building alone does not regenerate the keystore and debug key.
您可能会在到期日期之前获得相同的调试密钥，但不要依赖它。