Front calls changes

Modifications to consider when using front calls.

New front-calls

JSON data from mobile.getRemoteNotifications

JSON structure returned with GMA/Android

Starting with GMA 4.01.07, with the mobile.getRemoteNotifications front call, the structure of the returned JSON data for an FCM notification of type "message" has changed, maching the Firebase Cloud Messaging API V1 JSON used by the push notification send from the push server.

Before GMA 4.01.07, the structure of a JSON element a serialized JSON object in the "data" field, using a "genero_notification" member:
 {
  "type": "message",
  "data": "\"genero_notification\" : { \"title\" : ... }",
  "from": "764001239714"
 }
Since GMA 4.01.07, the "genero_notification" member is no longer used, and the "title", "content", "icon" (as well as the new "id") fields appear now directly under "data":
 {
  "type": "message",
  "data": {
           "id"      : "82837497234",
           "title"   : "Game Request!",
           "content" : "Bob wants to play poker...",
           "icon"    : "smiley",
           ...
          },
  "from": "764001239714"
 }

JSON structure returned with GMI/iOS

Starting with GMI 4.01.05, the JSON structure returned by the mobile.getRemoteNotifications front call contents two new members to identify notifications "id" and "sysId":
 {
  "aps" :
  {
    "alert" : "My first push",
    "badge" : 1,
    "sound" : "default",
    "content-available" : 1
  },
  "id":1,
  "sysId":"6A31016D-051E-4943-9111-E959241D3DCD"
 }

For more details, see mobile.getRemoteNotifications.

Changes in earlier versions

Make sure to check the upgrade notes of earlier versions, to not miss changes introduced in maintenance releases. For more details, see Front call changes in BDL 4.00.

Notable changes introduced in maintenance releases:
  • No particular change to consider.