In my application there is integration with VKSDK. Everything works when you compile from a computer. But when you drop the APK into google play and it is published, it turns out that when authorizing access to the VC key, it writes an error like the even there. But again, I repeat that when you start from a computer, then all the rules. What could it be?
Closed due to the fact that the essence of the question is not clear to the participants of Yura Ivanov , pavel , tutankhamun , fori1ton , Denis on Oct 5 '16 at 7:19 .
Try to write more detailed questions. To get an answer, explain what exactly you see the problem, how to reproduce it, what you want to get as a result, etc. Give an example that clearly demonstrates the problem. If the question can be reformulated according to the rules set out in the certificate , edit it .
- I think if you would have told a little more detail about “even the type there is wrong,” then the solution of your question would be accelerated. - post_zeew
2 answers
From the computer, you start the application signed with the default debug key. SHA-1 of this particular, debug key is yours and is specified in the application settings on the VK site.
In the market, you must upload the application signed with the release key. Those. You need to add a SHA-1 release key in the application settings on the vk.com website. Those. there should be two of them - for release and for debug
Get key fingerprint can be different. This is described in the dock . Here is the simplest option if the SDK is already connected to the project:
String[] fingerprints = VKUtil.getCertificateFingerprint(this, this.getPackageName()); - But in the same place only for one key there is a graph: "Certificate fingerprint for Android" ??? - sviter-pro
- @ sviter-pro, there is also a "add one more" button. In general, their number is unlimited - YuriySPb ♦
- I understand ... and where to get SHA-1 for release? Is it the same as the debazh? - sviter-pro
- Is it necessary to take it somewhere in google play? - sviter-pro
- @ sviter-pro, it should be received in the same way as the debugging one. There are several ways. Here, for example, a method from docks in VKSDK , there, by the way, about the release key is written. Read - many questions will disappear at once:
String[] fingerprints = VKUtil.getCertificateFingerprint(this, this.getPackageName());- Yuriy SPb ♦
Applications may be signed by different keys. When the application is installed after compilation in Android Studio, the apk file is also created and the installation itself takes place. What you did according to the instructions is the debug key and the API from vk.com will only work in the application if it was installed directly from Android Studio. In order for the API to work on the release apk files that will be distributed, you also need to add another release key to the site. You can get it almost the same way, the only thing you need to specify in the parameters for the command line is a specific keystore with which the application will be signed.