What’s new in Mobile Cloud for June

Share this post:

The newest version of the Mobile Cloud services is now available on Bluemix! If you’ve been with us since the Beta, there are several key items you’ll want to know about. The SDK has significant changes and new features were added to the services.

This post contains a general overview of the changes that were made to the Mobile Cloud SDK and services. If you want to start updating your apps right away, go to Migrating Mobile Cloud client applications from the Beta for all the details you need about the API changes.

Domain name changes
As announced previously, the default application route for your Mobile Cloud application is now:

Application secret
Your mobile cloud now includes an application secret. This value is displayed next to your application ID in the Bluemix dashboard page for your application, or in the MAS service configuration for your application. You must pass value of the application secret to the initialize method of your mobile client application. More details about the initialize method are in the Client SDK section. Be sure to keep your application secret value confidential. You can regenerate the secret from the Mobile Application Security service in your Bluemix dashboard.

The documentation URLs have changed. If you bookmarked pages during the Beta, be aware that these pages might not be up to date. You can find links to the updated documentation from the Bluemix dashboard. You can also visit the Mobile Cloud landing page.

The samples were updated to use the new SDK. To download the samples, go to @mobilecloud on IBM DevOps Services.

Client SDK – General

  • The core parts of the SDK were renamed from IBMBaaS to IBMBluemix.
  • The initializeSDK method was changed to initialize or initializeWithApplicationId. The method now takes three arguments: applicationId, applicationSecret, applicationRoute. You can find these values on the details page of your application in the Bluemix dashboard. You can also find the applicationSecret on the MAS service configuration for your application.
  • The ibmconfig template was merged into the Core SDK (and can be removed from existing applications).
  • The IBMCloudCode.initializeService() method no longer requires a host name.
  • IBMBluemix now supports getCurrentUser and getCurrentDevice methods after the setSecurityToken method is run.
  • The getVersion() method now includes a build number for tracking support calls.
  • Many API names have changed. For more details about the API changes, see Migrating Mobile Cloud applications from the Beta.

Client SDK – iOS

Client SDK – Android

Client SDK – JavaScript and Node.js

  • The CloudCode template has been enhanced to support more modular RESTful apps.
  • ibmconfig was removed and merged into the IBMBluemix.getConfig method.
  • IBMBluemix supports getting the IBMLogger with the getLogger method.
  • You must pass req to the initializeService method. Do not use the getService() call because there’s no longer just one “instance” of the service SDK.
    app.use(function(req, res, next){    <br /> = IBMData.initializeService(req);<br />  req.push = IBMPush.initializeService(req);<br />  next(); <br />});

Client SDK – Cordova

  • Apache Cordova is now supported as an s SDK client. The plug-ins can be installed into your Cordova project easily.
    cordova plugin add
    cordova plugin add
    cordova plugin add
    cordova plugin add
  • Cordova is supported on iOS and Android, and each plug-in contains the Native SDK and a JavaScript Shim for using the Plugin from the WebView.
  • The following features are not complete or supported in the Hybrid JS Shim:
    • IBMDataClientManager is not implemented
    • IBMFileSync is not implemented
    • Some aspects of IBMQuery are not implemented or supported
  • Hybrid SDK documentation

Client SDK – Worklight

  • IBM Worklight is a supported runtime for both the 100% JavaScript SDK and the Cordova based SDK. IBM Worklight does not support the latest Cordova plug-in architecture but the plugins can be installed manually, the manual instructions are documented in the Hybrid Getting Started Guide.
  • The following features are not complete or supported in the Hybrid JS Shim:
    • IBMDataClientManager is not implemented
    • IBMFileSync is not implemented
    • Some aspects of IBMQuery are not implemented or supported
  • Hybrid SDK documentation

Mobile Application Security (MAS)

  • You can now secure access to your Mobile Cloud services with Google+ or Worklight authentication.
  • In the MAS service instance in the Bluemix dashboard, you can see a list of devices and users that have accessed the Mobile Cloud applications.
  • You can disable specific devices and users from the MAS service instance on the Bluemix dashboard.
  • You can view and regenerate your application secret from the MAS service instance on the Bluemix dashboard.
  • The ibmsecurity server-side API has changed. Do not specify explicit authentication validators when you are adding the MAS middleware to express.
    Example: app.use(mas({client_white_list: true})); becomes app.use(mas());
  • Charts were added to the Analytics tab for MAS validation errors.
  • MAS documentation

Cloud code (Node.js server template)

  • The app.js template was refactored to be more modular.
  • The ibmconfig template was merged into the core SDK.
  • The ibmsecurity API is integrated to protect your endpoints.
  • Node.js for Mobile Cloud documentation

Mobile Data

  • There is now provisional support for serializing IBMGeometry classes that represent GeoJSON compliant geometries.
  • With provisional location storage and REST location query capabilities, you can understand where your users are and provide richer queries based on their location.
  • Added relation capabilities to capture the relationship between objects and query on the relationship.
  • The REST URL tab was removed because you can generate REST requests with the REST API documentation.
  • The Analytics tab for Mobile Data shows API breakdown by device details and filtering by resource.
  • Mobile Data documentation

Location (beta)

  • Location is brand new and currently in beta. All associated APIs are provisional and are subject to change.
  • Beta Location SDKs are bundled in the SDK download for iOS and Android.
  • You can use IBMPointOfInterest, an IBMDataObject specialization for defining points of interest.
  • Includes support for location acquisition and device triggers:
    • Geofence triggers: perform an action upon entering or exiting either a polygon or circular area.
    • Geodwell triggers: perform an action upon dwelling inside or outside of an area for a specified amount of time.
    • Location changed triggers: perform an action each time the device’s GPS location changes.
    • Location acquisition: Quickly start location acquisition with a predefined acquisition policy (for example: power saving, live tracking)
    • When acquisition is enabled, the IBMDevice object will be updated with the last known location.


  • You can now send push notifications by consumer ID and device alias (friendly name) across sandbox and production environments. Your enterprise applications no longer need to map device IDs with application user IDs (like employee ID, consumer ID, agent ID, and so on). You can address notifications based on these application object IDs, which is more natural for your data models.
  • The user experience of the Push service on the Bluemix dashboard was improved across production and sandbox environments to select and work with notification targets and device registrations.
  • The Analytics tab includes filtering for notifications by tags.
  • Push documentation

More stories
May 7, 2019

We’ve Moved! The IBM Cloud Blog Has a New URL

In an effort better integrate the IBM Cloud Blog with the IBM Cloud web experience, we have migrated the blog to a new URL:

Continue reading

April 30, 2019

Introducing IBM Analytics Engine v1.2 and Announcing the Deprecation of IBM Analytics Engine v1.0

We are excited to inform you about the new version of IBM Analytics Engine v1.2 that will be available starting May 15, 2019. Along with this release, Analytics Engine v1.0 will be retired.

Continue reading

April 23, 2019

Announcing the Deprecation of the Watson Machine Learning JSON Token Authentication Service

We’d like to inform you about the deprecation of the Watson Machine Learning JSON Token Authentication service. This method of authentication will be retired on May 30, 2019.

Continue reading