Was this article helpful?

Change Log

Last modified 07:03, 15 Jun 2014

Version 3.1 - 11 June 2014

  • Support for new Facebook SDK version 3.14 
  • Various bug fixes

 

Version 3.0 - 16 Feb 2014

  • GSAPI is now a singleton class, there is no need to maintain a single instance manually.
  • Gigya UI Plugins can now be displayed and used through the Android SDK, using the GSPluginFragment class.
  • Login/addConnection now uses the device browser instead of web view dialog by default. This can be controlled using the GSAPI.setLoginBehavior method.
  • GSEventListener has been deprecated and replaced by GSSocializeEventListener and GSAccountsEventListener.
  • Enhanced Facebook SDK integration:
    • Permissions no longer need to be specified in the login method. Facebook Native Login now uses the permissions configured for your site in the Gigya management platform.
    • Facebook Native Login behavior can now be controlled by passing a facebookLoginBehavior parameter to login methods.
    • Facebook login is now enabled only via Facebook Native Login, following Facebook's policy change.
  • Various bug fixes and stability improvements.

 

Version 2.15.9 - 20 November 2013

  • Added demo project
  • Minor bug fixes

 

Version 2.15.8.1 - 2 October 2013

  • Bug fix

 

Version 2.15.8 - 26 August 2013

  • Native login (SSO) providers are now optional - Facebook and Google+
  • SDK must be configured according to providers documentation
  • Native login does not use web view
  • New display for login UI
  • Bug fixes

 

If you want to upgrade an app that was developed with a version earlier than 2.15.8, use the Upgrading to 2.15.8 guide to migrate your code.
 

Version 2.15.7.1 - 16 May 2013

  • Updated the Google play services version.

 

 

Version 2.15.7 - 14 Apr 2013

 

Version 2.15.6 - 06 Nov 2012

  • The signature of the GSUIListener.onError event handler has changed. The method receives a GSResponse argument (instead of the errorCode and errorMessage parameters). This enables passing more information on error. The new signature is:

public abstract void onError(GSResponse res, Object context);
 

Note: this version is not backwards compatible. If you are upgrading from a former version and you are listening to the onError event, you should make the following minor changes in your event handler implementation:
1. Change the onError method signature to the one mentioned above.
2. In the method implementation, instead using errorCode and errorMessage parameters, use res.getErrorCode() and res.getErrorMessage() 

  • GSAPI.setAPIDomain - new method that provides the option to specify a data center to be used for making API calls. For example: "eu1.gigya.com" for Europe data center.
  • The targetEnv parameter (accepted by some of the Accounts API methods) is automatically set to "mobile" in all requests (there is no need to set it manually).

Version 2.15.4 - 28 Aug 2012

  • Support for the new accounts.login API method - the SDK stores the session info returned from the method on the device as GSSession.
  • Bug fix in GSSession when session expiration is not specified. Now if expiration time is not specified, it is set by default to infinity (max integer).

Version 2.15.3 - 21 June 2012

Bug fix for null pointer exception in getCookies.

 

Version 2.15.2 - 06 May 2012

  • Every socialize.getUserInfo request that is issued after a successful login, will be using HTTPS.
  • Bug fix for loop between GSWebViewActivity and the FB App, when enabling the "Don't keep activities" in the device's developer settings, on Android 4.0.3.
  • Bug fix for GSAPI.addConnection - it is now using Facebook's Single Sign-on.

Version 2.15.0 - 17 Apr 2012

  • The ​​GSAPI.logout method now logs out the user from the Social Networks.
  • Some API methods are considered to be global, for they are not associated with a specific user. Few examples of global API methods: comments.getCommentsreports.getSocializeStatssocialize.getFeed, etc.
    From this version on you may access the global APIs without having a logged-in user session.

     

     

Version 2.14.1 - 17 Oct 2011

Enabled GZIP compression.

 

Version 2.14.0.1 - 5 Oct 2011

GSAPI constructor accepts Context instead of Activity. Context is the base class of Activity, so backwards compatibility is kept.

This allows the GSAPI to be constructed by background services that don't have an activity to pass.

 

Version 2.14 - 19 Sep 2011

  • Fixed bug: session expiration was passed even if client asked for offline access, which caused our server to expire the session immediately.
  • login, addConnection, showLoginUI, showAddConnectionsUI methods - HTTPS is always used in the login/add-connection process.
  • Tracing is disabled by default, to reduce log clutter. You may enable tracing by setting GSAPI.OPTION_TRACE = true;

 

Version 2.13.4.1 - 28 Aug 2011

  • Fixed Facebook Single Sign-on permission bug.
  • Improved nonce generator to handle rare case of subsequent calls generating same nonce.

 

Version 2.13.4 - 14 Aug 2011

Note: this version is not backwards compatible. You may need to make minor changes in your code, if you are upgrading from a former version. Please follow the migration instruction below. Upgrading to this version is required, if you wish to integrate Gigya's Game Mechanics or the Gigya Cloud Storage platform.
  • GSDictionary class is deprecated, and is replaced by the following new classes:
  • GSObject - New class, used for passing parameters, for example when issuing requests or receiving response data.
  • GSArray - New class, used for passing Arrays, for example when issuing requests or receiving response data.

Migration Instruction

Search for all instances of GSDictionary class in your code. Replace each GSDictionary instance with GSObject, and each GSDictionary[] (array) with GSArray. For example:

Old Code (using GSDictionary):
// Publish User Action

// Defining the userAction parameter
GSDictionary userAction = new GSDictionary();

userAction.put("title", "This is my title");
userAction.put("userMessage", "This is my user message");
userAction.put("description", "This is my description");
userAction.put("linkBack", "http://google.com");
           
GSDictionary[] mediaItems = new GSDictionary[1];
mediaItems[0] = new GSDictionary("{\"src\":\"http://www.f2h.co.il/logo.jpg\", \"href\":\"http://www.f2h.co.il\",\"type\":\"image\"}");
userAction.put("mediaItems", mediaItems);

GSDictionary params = new GSDictionary();
params.put("userAction", userAction); // set the "userAction" parameter 

// 2. Sending 'socialize.publishUserAction' request
gsAPI.sendRequest("socialize.publishUserAction", params, null, null);

New Code (using GSObject and GSArray):
// Publish User Action

// 1. Defining request parameters
GSObject userAction = new GSObject();

userAction.put("title", "This is my title");
userAction.put("userMessage", "This is my user message");
userAction.put("description", "This is my description");
userAction.put("linkBack", "http://google.com");
			
GSArray mediaItems = new GSArray();
mediaItems.add(new GSObject("{\"src\":\"http://www.f2h.co.il/logo.jpg\", \"href\":\"http://www.f2h.co.il\",\"type\":\"image\"}"));
userAction.put("mediaItems", mediaItems);

GSObject params = new GSObject();
params.put("userAction", userAction); // set the "userAction" parameter 

// 2. Sending 'socialize.publishUserAction' request
gsAPI.sendRequest("socialize.publishUserAction", params, null, null);

 

Version 2.13.2 - 7 July 2011

  • Unhandled exception bug fix.

 

Version 2.13.1 - 29 June 2011

  • Fix for timestamp correction when device's local is not English
  • Automatic logging of response if errorCode != 0
  • To request permission for logged-in user, call addConnection, pass the required permission and set getPerms to 1

 

Version 2.13 - 26 June 2011

  • Added a new parameter canceled in the onClose event of showLoginUI and showAddConnectionUI. When the parameter is 'true' it indicates the UI was closed due to user canceling the operation.
  • Login and addConnection will return GSResponse with errorCode 200001, when users cancels the operation.
  • The SDKs can now automatically compensate for when the mobile device's clock is not synchronized.
  • When sending a request, if useHTTPS is set to 'true', the request is not signed and the secret key is passed instead - this saves CPU of calculating signature, since it's secured by HTTPS.
  • The SDK parameter sent to the server includes the SDK version: e.g. "iphone_2.13", "android_2.13", etc.

     
Was this article helpful?
Pages that link here
Page statistics
1917 view(s) and 11 edit(s)
Social share
Share this page?

Tags

This page has no custom tags set.

Comments

You must to post a comment.

Attachments