question

Hello Everybody. I spend a day or so wrangling with GameCircle and have come back from the desert to give you a solution to your potential Unity crashing woes. Minor trivia first: 1) Be sure your AndroidManifest.xml contains: Major trivia now: You will need to modify the following files: AGSProfilesClient AGSLeaderboardsClient AGSAchievementsClient They currently use a static constructor in which your JavaObject is initialized. We want to rename this to be a normal function (called, say: public static void Initialize()). We are going to assure that it is being called at the correct time. The functions will now look like: AGSProfilesClient.Initialize(); AGSLeaderboardsClient.Initialize(); AGSAchievementsClient.Initialize(); These classes inherit from Monobehavior. I added these to an object each in the hierarchy - named the same as the class. I do not know if this is mandatory - but it is a delicate ecosystem. Your workflow will should like this: 1) Application launches 2) Call AGSClient.Init and wait on your ServiceReadyHandler 3) When the ServiceReadyHandler returns positively: 4) Call AGSProfilesClient.Initialize(); 5) Call AGSLeaderboardsClient.Initialize(); 6) Call AGSAchievementsClient.Initialize(); 7) Register listeners for PlayerAliasReceivedEvent / PlayerAliasFailedEvent in AGSProfilesClient if you need to 8) At this point - you can now launch into your usual application logic. Open leaderboards, submit scores, update achievements. The critical timing here is: 1) Initialize 2) Wait for Service to be ready 3) When service is ready, initialize the three core classes above 4) Now that these are initialized, make whatever requests you like. I hope this is helpful to those of you wrangling with Unity issues! -JFFM [i][/i][i][/i]