I'm trying to get GameCircle to work correctly for my Unity app to no avail. I've followed all the directions on the "Setting Up Amazon GameCircle in Unity" page, and I've followed all the suggestions I've found here on the forums. I've even emailed support and got the exact same suggestions I saw in the forums, right down the spelling error of "keystone" rather than "keystore" and it is still giving me the CANNOT_AUTHORIZE error in logcat. What I'm looking for is a better explanation of the "Whitelist Registry" section of the "GameCircle" tab in the dev portal. What does "Package Name" mean? Is it the same as the App SKU? If it is, why not just say App SKU instead of "Package Name"? The signature from keytool has symbols like + and = in it. Are those supposed to be included when I'm whitelisting? Does having incorrect signatures affect the GameCircle authorization? Anyone from Amazon replying, [b]PLEASE[/b] do not respond with the general "follow these steps" post that I've seen three times already.
Package name is not same as App SKU. You can find the package name in your app's AndroidManifest.xml file as an attribute of tag. Also, symbols likes + and = are part of signature. Please include them while white-listing.
I also have the same problem ! The logcat is throwing me "D/AGC_ServiceProxy(17313): authResult: CANNOT_AUTHORIZE", ! I'm launching yours example project included in package for Unity sign with my own key. I don't maybe the problem is with key ? please provide us a correct steps to generate the correct key and process signing the apk.
My app is made in Unity. Does the package name in the AndroidManifest.xml file change when I build the project? Right now as I look at it, it says "com.unity3d.player" as the package name. Does it change to the "Bundle Identifier" field in Unity's Player Settings > Other Settings on build?
My problem was caused by OpenSSL provided by cygwin (I'm working on Windows). The OpenSLL from cygwin was generating the WRONG SIGNATURE! so beware what are u using to generate signature! Message was edited by: waskithebest
I asked other person to check command "keytool -exportcert -alias myAlias -keystore mykey.keystore | openssl sha1 -binary | openssl base64" with my keystore (on Mac) and he provided me a correct signature. So try it to execute this command on non-Windows platform.