Closed OmerCeliker closed 8 years ago
Thanks for the feedback. I have passed along the information, but I have not heard of any update yet.
Is it possible that that package name and SHA1 fingerprint have been registered before?
No. On Dec 22, 2015 2:36 PM, "Clayton Wilkinson" notifications@github.com wrote:
Thanks for the feedback. I have passed along the information, but I have not heard of any update yet.
Is it possible that that package name and SHA1 fingerprint have been registered before?
— Reply to this email directly or view it on GitHub https://github.com/playgameservices/android-basic-samples/issues/189#issuecomment-166711409 .
Let me correct my answer. I am not sure. On Dec 22, 2015 2:36 PM, "Clayton Wilkinson" notifications@github.com wrote:
Thanks for the feedback. I have passed along the information, but I have not heard of any update yet.
Is it possible that that package name and SHA1 fingerprint have been registered before?
— Reply to this email directly or view it on GitHub https://github.com/playgameservices/android-basic-samples/issues/189#issuecomment-166711409 .
You'd encounter this error when you are re-registering with the same package name (i.e when you delete a game service and add a new one with the same name ). Check if your project has been already registered in https://console.developers.google.com/ Any project you delete, takes effect only after 7-days.
Closing this one. Please reopen if you still cannot publish.
Hello,
I am getting the error title above, while I try to add google play services to my application using google play developer console->Game Services->Mochiland->linked apps->authorize your app now
I have already submitted another bug report for this but did not hear from anyone at google yet. The package name is com.jujubiz.mochiland
I was trying to enable the advertisement for Ads Badging. It will not let me save the flag for it unless I have the game services working first. I am stuck at the moment.
Can you make your error messages more descriptive overall? Google should have a lookup table for all its error messages.