Push Notification Services v1.8

Push Notification Service Release Notes


Release Date: March 2017

Bug Fixes

Fix an issue when upgrading the Push tile on PCF v1.9.

Known Issues

Push Scheduler and Push Service Broker are not compatible with any PCF that includes ruby-offline-buildpack version greater than 1.6.39. To find out which release contains the appropriate ruby-offline-buildpack, see the Pivotal Elastic Runtime Release Notes.


Release Date: February 2017


Ability to customize push app instance counts during deployment. For more information see custom deployments.

The Push Dashboard will now show a warning when the iOS certificate in use is expired.

Official support for Azure.

Bug Fixes

Known Issues

Upgrading to Push 1.8.0 when running on PCF 1.9 may fail with an error Server error, status code: 500, error code: 10001, message: An unknown error occurred.

This is due to the 1.8 version of the push tile defaulting to 2 app instances for each application it deploys on the system org, push-notifications space. This error is encountered when an app is staged and scaled at the same time.

Please upgrade to version 1.8.1 to fix this issue.

Workaround: Update the instance counts of the apps under the system org, push-notifications space to 2 each before installing Push 1.8.0 (or the custom instance counts if you’re using that option.)


Release Date: January 2017

Bug Fixes

Fix the ability to edit scheduled pushes


Release Date: December 2016


Support for Android FCM push notifications

Bug Fixes

Dashboard session timeout error

Known Issues

Once a scheduled push is created, it cannot be edited (will address this bug in a later release)


Release Date: September 2016

Updated stemcell to v3263 to address kernel vulnerabilities (includes 4.4 kernel)


Release Date: September 2016

Note: Update to Push Notification Service v1.6.2 prior to upgrading to Pivotal Cloud Foundry v1.8.

Updated stemcell to v3263 to address kernel vulnerabilities (includes 4.4 kernel)


  • Fixed dashboard issue found when upgrading from PCF v1.7 to PCF v1.8

Known Issues

If you installed Push v1.6.2+ after upgrading to PCF v1.8, then remove the app named push-notifications-analytics with the following command:

$ cf delete push-notifications-analytics


Release Date: August 2016


  • Proxy support in Push Tile: Users can now add a proxy in the Push Tile (via Ops Mgr console)
  • Installation logs now available in Ops Mgr console upon installation failure fixes


  • Fixed issue with multiple tenants being provisioned in system org in push notifications space
  • Fixed scaling issue with push api instances due to lack of database connections

Known Issues:

Upgrading to PCF v1.8 exposes a bug in versions of Push v1.6.1 and older. The impact is that the dashboard won’t be able to display analytics (a message will appear stating “Analytics Data is not available at the moment”). Analytics data is still collected on the backend, the bug prevents it from being displayed.

The recommended solution is to upgrade to push v1.6.2 prior to upgrading to PCF v1.8 (this is now a pre-requisite for PCF v1.8)

If installing push v1.6.1 or earlier on PCF v1.8, follow the instructions below

  1. To confirm this is the problem you are experiencing, you can check to see if there is a CF app running in the system org and push-notifications space called push-notifications-analytics.

  2. Replace push-analytics with push-notifications-analytics and add a matching route as per the commands shown below

 cf delete push-analytics
 cf rename push-notifications-analytics push-analytics
 cf map-route push-analytics $ENV_URL --hostname push-analytics

where $ENV_URL is the value of the domain name used for your PCF environment


Release Date: July 2016

  • Devices can be grouped under Custom User IDs which can be targeted for pushes
  • Tags have been replaced by Topics
  • Topics can be created with expiry dates


Release Date: December 2016

Security release for CVE as detailed in USN-3156-1


Release Date: December 2016

Security release for CVE as detailed in USN-3151-2


Release Date: June 2016

  • Bug fix for Service broker bug with HTTPS


Release Date: June 2016

  • New Heartbeat Application is deployed with the Push Notifications Service
  • Heartbeat Monitor App available on iOS and Android


Release Date October 2016


Release Date October 2016

  • Bump Ubuntu stemcell for USN-3099-2: Linux kernel (Xenial HWE) vulnerabilities


Release Date: October 2016

  • Updated Ubuntu stemcell for USN-3087-2: OpenSSL regression


Release Date: June 2016

  • Updated BOSH stemcell to v3262.2
  • Bug fix for cf CLI


Release Date: June 2016

  • Security release requiring stemcell v3232.8


Release Date: June 2016

  • Security release requiring stemcell v3232.6
  • Bug fix for Service broker bug with HTTPS


Release Date: May 2016 - Security release requiring stemcell v3232.2


Release Date: May 2016 - PCF v1.7 compatibility. - Update to this version of push before updating to PCF v1.7.0


Release Date: March 2016 - Security release requiring stemcell v3146.10.


Release Date: February 2016 - Security release requiring stemcell v3146.8.


Release Date: November 2015

  • The Push Notifications Service now supports multiple tenants.
    • Push Notifications is now a service that can be provisioned from the CF Marketplace.
    • The dashboard now requires a Tenant Id.
  • The dashboard now displays logs related to push activities.
  • The analytics system now configures a second Redis to behave as a cache for storing logs.
  • Update to the Push SDK supports iOS 9 and includes a Swift sample app.
  • The Push SDK for Android now supports Android 6.0 Marshmallow, including the new permissions system.
    • See the Push Sample app for an example of Android 6.0 Marshmallow permissions.


Release Date: October 2015

  • Support for PCF v1.6 and Diego.
  • SOCKS proxy bug fix.


Release Date: October 2015

  • Bug fixes for smoke tests.


Release Date: September 2015

  • Bug fixes for certain scenarios regarding expiry time.

v1.3.3 iOS and Android Client SDK

  • Push app analytics.
  • Custom HTTP request headers.
  • Custom SSL authentication.


Release Date: August 2015

  • Deprecated lucid64 stack in favour of the new Trusty/cflinuxfs2 stack
  • Proxy Support for iOS push notifications. Supports SOCKS proxies.
  • Proxy Support for Android push notifications. Supports HTTP and SOCKS proxies.

v1.3.2 iOS and Android Client SDK

  • Enable and disable geofences at runtime.
  • Added a method to read the device UUID at runtime.


Release Date: August 2015

  • Support for RabbitMQ Service versions v1.4.0 and later
  • Tag management added to dashboard
  • Ability to regenerate push api keys
  • Minor improvements to installation
  • Allow certificate checks to be disabled in cf environments that use self signed certificates

v1.3.1 iOS and Android Client SDK

  • SSL Certificate pinning.
  • Any geofences with tags will be monitored only if the user is subscribed to that tag.


Release Date: June 2015

  • Location based notifications
  • Android and iOS support (SDKs)
  • Dashboard support
    • Maps
    • Saved locations and groups of locations
    • Active geofences view

Upgrading from version v1.2.x to v1.3.0


Release Date: April 2015

  • Offline installation support


Release Date: March 2015

  • Scheduled push notifications
  • Notifications with expiry time
  • Updated UI/UX for dashboard (sending scheduled push with expiry time)

v1.1.0 - January 2015

v1.0.1 - November 2014

v1.0.0 — July 2014

Create a pull request or raise an issue on the source for this page in GitHub