It is only used as a personal study record. If there is any infringement, please notify me to delete it in time
From: http://bbs.lbsyun.baidu.com/forum.php?mod=viewthread&tid=106461
Security code verification tool:
http://bbs.lbsyun.baidu.com/forum.php?mod=attachment&aid=MTUwMDZ8ZmUzNTBjYTR8MTQ5OTI2MTU2N3w5Njk0NzJ8MTA2NDYx
In view of a large number of key verification failures in the Android SDK, they are basically caused by incorrect package name or SHA1 filled in when applying for AK in the API console ( see the official tutorial for the package name or SHA1 acquisition ). Search the log, if " Authentication Error errorcode: 230 uid: -1 appid -1 msg: APP Scode verification failed " appears, read the following carefully. If you want to quickly solve the verification problem, you can use the security code verification tool provided below to obtain the correct package name and SHA1 value of the APP, and update these two values to the AK corresponding to the API console . Security code proofing tool : MCodeCheck.zip (363.22 KB, Downloads: 8402) . After opening the application, find the APP developed by yourself (the latest installed APP is at the top by default), and after clicking it, a dialog box will pop up to display the package name and SHA1 value.
Special attention: Do not update the AK used in the APP that has been released online, otherwise, the authentication of the APP that has been released may fail. For details on how to obtain SHA1, please refer to: Android Studio and Eclipse forDistinguish between debug version and release version signature files. Special attention for developers:Many developers have debug version and release version signature files to package apk separately. The installed app ispackaged with the signature file of the debug version, and the SHA1 of the debug version is obtained here; on the contrary,if the app you installed ispackaged with the signature file of thereleaseversion, the SHA1 of the release version is obtained here. In the API console,the SHA1 value corresponding to the debug version signature file is filled in "Development version SHA1"; similarly,release version signature fileis filled in "Release version SHA1",which can ensure that it is used during development and testing. The same AK will do. Debug version signature file:refers to the signature file used by the apk that is directly debugged and run from Android Studio or Eclipse during the development process, and is generally processed automatically by the development tool. Release version signature file:refers to the signature file that is packaged by selecting the specified signature file when submitting the test or release. Generally, the same APP uses a unified signature file.