0

I know there are some posts about this issue,such as this one and this one.

But my case is a bit special. Because the same source code works for another package name. So I think the only possible reason could be the google console setup. Here is the screenshot of my setup:

enter image description here

The first one is my testing version package name which works perfectly. The second one is my real package name which got the authorization failure. I'm using the debug.keystore to generate the sha1. And I did try to create a separated Android Key for my real package name. But I got the same error.

Does anybody can give me a hint? Thanks.

Community
  • 1
  • 1
Bagusflyer
  • 12,675
  • 21
  • 96
  • 179
  • in the second package, are you still using debug keystore or you have a release keystore? – Jeongbebs Dec 05 '13 at 03:14
  • I'm using the debug keystone for the second package. By the way, the problem is gone after I uninstall the application in device and rerun it. (Clean or rebuild doesn't work for me. Have to uninstall the app in device. Doesn't know why.) – Bagusflyer Dec 05 '13 at 04:07

0 Answers0