GameCircle now covers all Android devices!

ar2rsawseen

@SinisterSoft even more I can't find download link from their website to full SDK, only to Ads only version, so I don't know if that is just an rearrangement of the website, or something more

SinisterSoft

Here is the link to the last version I could find:

http://d2jks9au6e6w94.cloudfront.net/sdk/heyzap-sdk-6.4.1.zip

SinisterSoft

I asked heyzap support about this, they replied:

" Hi Anthony,

Thats correct. We no longer support leaderboard+achievements.

You can still use us for advertising. Let me know if you have any other questions.

Cheers,
Immad
"

@ar2rsawseen - you might as well not support heyzap then....

I'm taking it out of my stuff.

SinisterSoft

btw, in the Gamer lib, within the frameworks folder you have GameTest, GameHelperUtils and GameHelper - should they not be in the folder above - they are not frameworks?

SinisterSoft

Also, will the next version of iab have a frameworks folder (it's a good idea imho).

ar2rsawseen

btw, in the Gamer lib, within the frameworks folder you have GameTest, GameHelperUtils and GameHelper - should they not be in the folder above - they are not frameworks?

GameTest is a test interface for testing the plugin related code (not specific framework related code), I forgot to remove it
And yes GameHelperUtils and GameHelper are only Google Play relayed, will rearrenge them

And true about iab

SinisterSoft

SinisterSoft

GameHelperUtils and GameHelper maybe should have googleplay_ before the filename? and still be in frameworks then?

ar2rsawseen

Updated gaming interface:

version 0.3
Updated GameHelper to latest version
Moved GameHelper to separate folder
Moved Amazon GameCircle to authentication workflow (now need to call login)
Added Cloud sync for Google Play libs and Whispersync

@MobAmuse for you there might be 2 reasons
1) I forgot to add ACCESS_NETWORK_STATE permission to example manifest
2) some methods would not work and might crash if amazon gamecircle was not yet loaded

for the second reason I'm implemented amazon gamecircle into login workflow

basically you need to call login and wait for call back before doing anything else:

local game = Gaming.new("gamecircle")   game:addEventListener(Event.LOGIN_COMPLETE, function() print("login complete") --game:reportScore("leaderboardId1", 10, true) --game:showLeaderboard("leaderboardId1") --game:updateState(1, "state2") --game:loadState(1) --game:resolveState(1, "1", "state3") --game:deleteState(1) end)   game:login()

SinisterSoft

I'm getting these errors with the new lib...

Any ideas on how to do a quick fix?

ar2rsawseen

Ah yes sorry, you can insert any numbes (for example 0), so it will use fallback strings.
Let me reupload that quickly

ar2rsawseen

Uploaded

SinisterSoft

SinisterSoft

Noticed that STATE_ERROR has no error message - but the other error events do.

ar2rsawseen

whoops, forgot to add it in docs, it has error property actually

SinisterSoft

SinisterSoft

The actual lib (not tested states yet) seems to work fine - tested on a few devices - no crashes. Just needs more docs I think.

ar2rsawseen

I've run into one problem, but it seems to be relative only to me, as no one seems to have anything like that, will try submitting an app to amazon and see what their testing team will say

SinisterSoft

What is the problem?

ar2rsawseen

It provides login error with CANT INITIALIZE and then displays the popup and initializes correctly, but does not dispatch logincomplete event anymore

SinisterSoft

I haven't had that.

ar2rsawseen

Yes I did not have that when I was testing either, but then created release api_key for app I wanted to submit and it happens every time

Maybe something is still not propagated on their server

SinisterSoft

When trying to load from google I get this crash when loading data with a key value of 4:

03-19 15:29:46.775: E/ParseService(32736): onStartCommand() - return START_STICKY
03-19 15:29:47.950: E/AndroidRuntime(32558): FATAL EXCEPTION: GLThread 232171
03-19 15:29:47.950: E/AndroidRuntime(32558): java.lang.IllegalStateException: State key is out of bounds: 4 is not between 0 and 4
03-19 15:29:47.950: E/AndroidRuntime(32558): at android.os.Parcel.readException(Parcel.java:1439)
03-19 15:29:47.950: E/AndroidRuntime(32558): at android.os.Parcel.readException(Parcel.java:1385)
03-19 15:29:47.950: E/AndroidRuntime(32558): at com.google.android.gms.internal.de$a$a.a(Unknown Source)
03-19 15:29:47.950: E/AndroidRuntime(32558): at com.google.android.gms.internal.dc.b(Unknown Source)

are the key values allowed only 1 to 3 ?

Google say

"Four slots, each with 256 kilobytes of storage (total storage size of 1024 kilobytes), no impact on the user's Google Drive quota"

Or is this referring to a different key?

SinisterSoft

Tested: Looks like key values can be 0 to 3 else crash 9 (on google)!!!

SinisterSoft

I also get this:

03-19 16:03:36.500: E/DataBuffer(4378): Internal data leak within a DataBuffer object detected! Be sure to explicitly call close() on all DataBuffer extending objects when you are done with them. (com.google.android.gms.appstate.AppStateBuffer@427d8760)
03-19 16:03:36.500: E/DataBuffer(4378): Internal data leak within a DataBuffer object detected! Be sure to explicitly call close() on all DataBuffer extending objects when you are done with them. (com.google.android.gms.appstate.AppStateBuffer@427f2280)
03-19 16:03:36.500: E/DataBuffer(4378): Internal data leak within a DataBuffer object detected! Be sure to explicitly call close() on all DataBuffer extending objects when you are done with them. (com.google.android.gms.appstate.AppStateBuffer@427f1b48)
03-19 16:03:36.500: E/DataBuffer(4378): Internal data leak within a DataBuffer object detected! Be sure to explicitly call close() on all DataBuffer extending objects when you are done with them. (com.google.android.gms.appstate.AppStateBuffer@427ef508)

ar2rsawseen

@SinisterSoft
1) yes from 0 to 3 should work
2) This is their internal bug and should be fixed in next Google Play Service version

SinisterSoft

On amazon I get a STATE_LOADED message after saving a state for some reason - it then result in a crash - but a normal state load doesn't crash.

SinisterSoft

2) <-- do you mean the crash or the memory allocation?

ar2rsawseen

2) memory allocation

ok let me check the crashing

SinisterSoft

Also I've noticed that sometimes I get a google login, then almost immediately a logout event, it's pretty rare though. googe:login() doesn't work after this happens.