Can only use one .p12 Certificate file at a time? For Push

Previously had my Development .p12 file uploaded, so Push worked while developing the app. But now I need to use the Production .p12 (so I can beta test to users via Apple TestFlight).
It appears, though, that Backendless only handles one .p12 at a time (either Development or Production); I cannot upload both.
So how am I supposed to debug / continue developing with push notifications (which needs the Development .p12) if I also need the Production .p12 to be active for those beta testing my app?

http://support.backendless.com/public/attachments/fb0a18195a6c44ebb9ba77b4bf1018fe.png</img>

fb0a18195a6c44ebb9ba77b4bf1018fe.png

Hi,

You should follow this guide with some changes below.

If you need the development and distribution .p12 at the same time, first you should create “Universal” (SandBox & Production) Certificate in your Apple Member Center (it is included in Xcode 7) for your Bundle Identifier:
http://support.backendless.com/public/attachments/00aa14e0705b020ed4ecfc1ddb25af49.png</img>
and then create .p12 file based on it.

Second, in Build Settings - Code Signing of your project target you have to set “iOS Distribution” option:
http://support.backendless.com/public/attachments/9a8c5c05822567e13c98d0917a38c229.png</img>
So, try this and let us know how it goes.

Regards,
Slava

You can create a new version of the same app. Use one version of development and the other one for production.

Mark

This solution unfortunately doesn’t work for embedded binaries, such extensions or widgets. Just tried.

So, please correct me if I’m wrong, I can’t debug push for an application in production, I mean with the real users data?

If you run your app from XCode with the “Distribution” provisioning profile, you can certainly debug anything you need.

Mark,

this is currently not possibile if you have app containing embedded binaries, such as extensions or widget. Don’t know if it is an Xcode issue or intentional behavior from Apple, but for this kind of product this solution is not applicabile.
Of course we can create a separate target without embedded binaries just for debug the push system. As you can understand this is sub-optimal.

This is a solution more than adeguate for app refactoring or major release. I understand your intentions and appreciate a lot this feature, but using it just for push debug purpose seems a poor application of the feature. Another issue with this solution is that is not applicable with real users data, since the two versions have separate data; not always we can afford such a rigorous product management system, sometimes we just want to try to solve little bugs. Software goes like that, doesn’t it? :wink:

ps: In this first approach with Backendless I seem very hostile about you product but, believe me, I’m loving it very much; I’m just try to cover what is crucial for us before migrating existing product or starting new ones.
Best regards
Michele