Update: Changes to Permissions Required for Push

Platform Services

As you may have read in my blog post published in November, there have been some changes to the way Push is handled in BlackBerry 10; namely, new permissions need to be specified both within the application as well as to the code signing keys being used.

Up until now, the new permissions for code signing had to be requested either when signing up for a Push Services account or via email, providing your code signing key information. I am happy to say that as of Wednesday January 2nd, this process is no longer needed, as all BlackBerry 10 code signing keys have been granted push permissions. This change means that you will no longer need to manually request that the permission be added to your keys before you can test push. Moving forward, all new keys will have this permission added automatically; at first within a few hours of the keys being issued, and soon after the delay will be removed entirely so the permission gets applied as soon as keys are created.

Developers will still need to add the Push Permission request to their application either by adding it directly to the bar-descriptor.xml file:

<action system=”true”>_sys_use_consumer_push</action>

…or, in the case of Cascades when using the Native SDK, by checking off the permission in the bar-descriptor.xml GUI editor:


Also, any existing debug tokens created prior to this permission being applied will need to be recreated in order for push to begin working.

So there you have it – one less step to get developing your push-enabled application for BlackBerry 10. All you need to do is sign up for an account (if you haven’t already) and get coding!

If you have any trouble, we have a host of samples up in Github and support will be actively monitoring the Push forum board.

Cascades Samples:

HTML5 WebWorks:

Adobe AIR:

Support Forums:

Join the conversation

Show comments Hide comments
+ -