iOS Aurora push Notifications

iOS Aurora push Document

First, create the project

Product Name:baixin

Company Identifier:com.bluewave

Bundle Identifier:com.bluewave.baixin

II. Certificate of Application

1. Create an Application ID

A. Log in to iOS Dev Center to opt into iOS Provisioning Portal.

b In IOS Provisioning portal, click App IDs to enter the app ID list.

C. Create App ID and skip this step if ID already exists

D. Refine the APP ID information and submit it as appropriate, and note that you need to specify a specific Bundle ID to avoid using wildcard characters.

Note: This error indicates that you have the same app ID and you do not need to create

E. Enable the Push Notification feature for the App. If you have already created an App ID, you can also turn on the Push Notification feature by setting it up.

F Go to this app ID to create it, then click Submit directly.

2. Configure and download certificates

A If you have not created a Push certificate before or want to recreate a new one, please create it under the list of certificates.

b New certificate requires attention to select a certificate type (development certificate for development and debugging use, production certificate for APP Store release)

Note: When publishing an app, all 4 certificates need to be created, and when tested, only two will be available.

C Click Continue to select the app ID for the certificate, and then continue with "about Creating a Certificate Signing Request (CSR)."

D Click Continue to follow this step

E Create a Certificate signing request (CSR)

F. Click Continue and save a. certsigningrequest CSR file.

G Continue with the D step above, add the. certsigningrequest, and then go to the following page

H This step is done 4 times to create a good certificate.

3. Export the. P12 certificate file (two are exported)

A Double-click the push certificate, and in Keychain Access your certificate appears in my certificates, note select mycertificatesandlogin, select the certificate file when you export the certificate, and do not expand private key.

B. Click Export and name the XXX.P12 file

C. Click Save, the window will appear, the password here can not be set, the next step directly. But if you set it up you have to remember that you need to use it later to create the app ...

4. Create a configuration file (Provisioning Profiles)

A Here at least one develops, one produces

b Next

C Choose the device you want to run here, you can select only one, and when you're not sure, you can all choose ....

D Now the configuration file has been built, download and save just fine ....

Hehe .... The following is the creation of all the certificates ....

OK ~~~~~, certificate and so on, the following to upload the certificate ....

Third, upload the certificate

A Https://www.jpush.cn/apps/new into the Aurora push page. (Register an Aurora account first)

b Create an App

Now that the application is created, the next step is to change some of the settings in the project ....

Iv. operation of Engineering documents

1. Import API Development Package to application project

A. Unzip the SDK package and select "Add Files to ' Your project name ' ..." in Xcode to add the extracted Lib subfolders (including APService.h, LIBPUSHSDK.A) to your project directory.

2. the necessary framework

• Cfnetwork.framework
• Corefoundation.framework
• Coretelephony.framework
• Systemconfiguration.framework
• Coregraphics.framework
• Foundation.framework
• Uikit.framework
• Security.framework
• Libz.dylib

3.Build Settings

A. Set the User Header search Paths and the Library search Paths under Search Paths, such as the SDK folder (the default is Lib) and the project file in the same level directory, are set to "$ (srcroot)/[folder name]" Can.

4. Create and configure the pushconfig.plist file

A. Create a new property list file in your project and name it Pushconfig.plist, and fill in the App_key parameters provided by the portal for your app.

{ "Aps_for_production =" 0 "; "Channel" = "Publish channel"; "App_key" = "AppKey copied from Jpush Portal application"; }

• CHANNEL
  • Indicates the download channel of the application package for easy channel statistics. Define it according to your own needs.
  • App_key
    • Automatically generated when an app is created on the management portal (AppKey) to identify the app. Make sure that the AppKey in the in-app configuration is consistent with the AppKey generated when the 1th step is created on the Portal, AppKey can be queried in the application details.
  • Aps_for_production
    • The 1.3.1 version is added to indicate whether the app is published with a production certificate (Ad_hoc or app Store), 0 (the default) is a developer certificate, and 1 is a production certificate publishing app. Please note that this configuration matches the Web Portal app environment settings.
  • In 1.2.2 or previous version of the configuration file, there is test_mode this key, the new version of the SDK is no longer used, you can delete it.

5. Add critical code

1.-(BOOL) Application:didfinishlaunchingwithoptions: In the method:

V. Common Mistakes

1.

Workaround:

2. After clicking the notification to enter the app, the message of the notification bar is deleted, and the badge number on the app is 0

Workaround:

Attention:

1. For badge number, the background is required to set +1 or-1 on push.

2. For the production environment or the development environment is set by the background

3. Client needs to pass tag, alias to server

4. If you switch User A/b on the same application, the alias of the first user is overwritten by the second alias, but the first user's offline message is still valid, which allows you to set the offline save time to a long point

iOS Aurora push Notifications