The gist of it though is that we were able to get it working despite the huge hassles. The main issue here isn’t the lack of documentation, its the over abundance of irrelevant, conflicting and misleading documents about a multitude of separate features of push related functionality on Blackberry devices.






So we decided to use this chance to go over the whole process of creating a push application for iOS, Android & RIM.






First there are several prerequisites you will need in order to get started with push:

• 
  Android – you can find the full instructions from Google
  
  here
  
  . You will need a project id that looks something like this:
  
  4815162342.
  
  You will also need the server key which looks something like this: AIzaSyATSw_rGeKnzKWULMGEk7MDfEjRxJ1ybqo.

• iOS – You will need to create a provisioning profile that doesn’t have the * element within it. For that provisioning profile you will need to enable push and download a push certificate. Notice that this push certificate should be converted to a P12 file in the same manner we used in the signing tutorials. You will need the password for that P12 file as well. You will need a distribution P12 and a testing P12. Warning! The P12 for push is completely different from the one used to build your application, don’t confuse them!
  
  You will need to place the certificate on the web so our push server can access them, we often use dropbox to store our certificates for push.

• Blackberry – you need to register with Blackberry for credentials to use their push servers
  
  here
  
  . Notice that initially you need to register for evaluation and later on move your app to production. This registration will trigger an email which you will receive that will contain all the information you will need later on. Such as your app ID, push URL (which during development is composed from your app ID), special password and client port number.
  

To start using push (on any platform) you will need to implement the PushCallback interface within your main class. The methods in that interface will be invoked when a push message arrives.:

Other than that we need to send various arguments whether this is a production push (valid for iOS where there is a strict separation between the debug and the production push builds) as well as the variables discussed above.

We must define the following build arguments in the project

properties:

ios.includePush=true

rim.includePush=true



rim.ignor_legacy=true



rim.pushPort=…



rim.pushAppId=…



rim.pushBpsURL=…







Once you define

all of these push should work for all platforms.

We hope this small guide has made the development of a push enabled application a bit simpler.