How to Test iOS Remote Notification
Configure up iOS Remote Push Notification
This document is applicable to applications created with Mobage Native SDK or Mobage Unity SDK.
For ngCore Applicaiton the process is slightly different from the process described below.
At the beginning, iOS developers need to generate push notification configuration (Apple App ID, SSL certificate, provisioning file) on https://developer.apple.com/, there is no need to operate on iTunesConnect.
1）Developers should create Apple App ID under their Apple Developer Portal, for example "cnhellokitty". And developers also need to set a unique bundle identifier for this App ID. Please do not occupy the official bundle identifier defined by Mobage. Here we set it as "kitty.hello.cn".
2）Developers should select "Enable for Apple Push Notification service" to enable push notification, which is related to the Apple App ID (in red). Click the "Configure" button for generating "Development Push SSL Certificate", which is indispensable to remote push notification test under Mobage sandbox environment.
3）Before clicking "Configure" button, developers need to generate a new certificate request from local "Keychain Access" on the Mac machine. Click the "Keychain Access" on the menu bar, select "Certificate Assistant", and then "Request a Certificate from a Certificate Authority…".
After inputting the email and name, and deciding the key pair information (2048 RSA), developers could get a file ended with .certSigningRequest.
4）And then, the certificate could be generate by clicking "Configure" button.
Please choose the .certSigningRequest file which has been just created.
By this step, a new certificate has been created and could be downloaded.
5）At last, developers should go to generate a new provisioning file. Developers need to input the profile name and select the Apple App ID (here is "cnhellokitty"), after choosing the relative developer certificates and devices, a new Development Provision Profile is ready for downloading.
Upload .p12 file to DeNA Developer Site
Developers should get two file now: one is certificate and the other is provisioning file.
Double click the certificate downloaded to the local request machine, and it will be imported to "Keychain Access". Please expand the certificate, and export both the Certificate and Key (it is the Common Name in Certificate Information) as a .p12 file.
Do NOT set password when exporting p12 file.
Pass this .p12 file to DeNA Developer Support (Contact via support center).
Sign the Application
Developers could use their own Apple developer certificate and provisioning file just generated to sign the application binary file with its own bundle identifier, which is only usable in Sandbox environment.
- Check the "conf.json" file, make sure that the "environment" is "SANDBOX".
- Check the bundle identifier is right. (Here is "kitty.hello.cn").
- Set the iPhone Developer and relative Provision file in the Xcode project settings, and then build the code to a binary file.
- Developers could use their test devices to install the binary file. And test remote notification with the Restful API provided by DeNA.
As the Sandbox application is managed by developers themselves, this binary file has no need to upload to DeNA Developer Site. Bundle identifier of a sandbox application doesn't need to conform to DeNA's bundle identifier naming convention.
For ngCore application, developers need to upload their ngCore game archive to DeNA Developer Site, to have it packaged into an iOS native application by Developer Site. Download the iOS native application (for sandbox), modify bundle identifier into what developer set on https://developer.apple.com, re-sign the application with push notification entitlements on a MAC machine.