iOS push certificates and passwords

General
1

Hi,

We’re working on migrating an existing app from Parse to Backendless, and cannot get push notifications to work.

We are using the same provisioning profiles and aps certificates that we use with Parse, and pushes work normally from the Parse console, but are not being received by the device from Backendless console. The device ID and Token are being created and displayed properly on Backendless, but no messages are received on the device. We have both a development cert and a production (universal) .p12 cert, both work correctly from Parse (which allows multiple certs). We tried uploading to Backendless first the production (universal) cert, and when that failed to work, uploaded the development cert, and that also fails.

At this stage of troubleshooting the problem, I have 2 questions:

  1. Is there some way to see which certificate is currently being used by Backendless? Only the message, “certificate file found” is displayed.

  2. Does Backendless “require” a password, even if there is no password associated with the cert? I believe it is fairly common among iOS developers to NOT associate a password with .p12 certificates (since that introduces another possible source of trouble in the always-arduous process of getting iOS pushes to work) and we would prefer not to risk making new certificates (i.e., with passwords) for our “live” app if we don’t have to. If Backendless does “require” passwords, then our next step will be to try to export new certificates with passwords.

Thanks so much for your help,

Rick

2

Hi Rick,
Please, investigate this doc. You could also try our PushNotify sample with your cert.

3

Thanks for your message. We have reviewed the document again, and still have the same question.

Can you tell us if Backendless must have a password for a .p12 certificate to work properly, even when there is no password associated with that cert?

Passwords are not required for .p12 certs on Parse, so we are just trying to determine whether it is the lack of password that is causing our problem on Backendless.

Thanks again for your help,

Rick

4

For Backendless Messaging you should use cert .p12 with password.