1. How long after the submission of the . P12 document can it be tested
The test can only be tested about 10 minutes after submission and is not effective immediately。
2. Applications are not receiving messages at backstage, i. E. Apns messages are not receiving them
1. To check the correct binding of cid and appid。
2. On the basis of the cid, he went to see whether the cid and the devicetoken were correctly bound。
3. See if certificate upload error
4. For service delivery, check if offline time is set。
What about three, devicetoken and clientid
The reasons for this are as follows: following a change of certificate environment, devicetoken has changed, but the cid has not changed so that it will not immediately be retied (usually after 24 hours) and the service-end records are the same as the original devicetoken. The solution is as follows: a gxsdkconfig. Plist file is required to be placed back in the project, packed, unloaded and re-installed. The change in cid would re-coup devicetoken, so that it would not be problematic。
4 when issued to appstroe, does the certificate environment need to be replaced
1. A development certificate is to be uploaded at the time of its development, and once the development test has been completed, the certificate will need to be replaced by a production certificate, which will take effect approximately 10 minutes after its replacement。
2. On apple equipment, the cid is the only one that is generally unchanged and does not recommend the regeneration of the cid。
3. In the case of an error in binding cid and devicetoken, a cid needs to be regenerated to facilitate testing of the operating methods: gxsdkconfig. Plist files are needed to repackage and unmount the original application to re-install the new package。
5. How long after the change of certificates will the client be rebound
Once the certificate has been replaced, it will not be again until 24 hours, at which point devicetoken will change. If tested within 24 hours, the message could not be received due to problems with the binding of clentid and devicetoken, as the change in the certificate changed and did not update the server, leading to the error of the server query。
6. Invalid devicetoken issue
1. Generally, the issue of the certificate environment, which results from the replacement of the certificate environment。
See if there is any problem with the binding of clentid and devicetoken。
3. See whether the local certificate environment is consistent with the certificate environment uploaded on the platform。
4. Check for expiry of the certificate。
Why do ios clients get two identical messages
1. This was due to the binding of two clientids by a devicetoken。
2. Clentid and devicetoken were bound by a change in the certificate environment, but the service-end data were not updated or tied to the old devicetoken. When the new clintid is obtained with a plist file, the new and old clintid will be re-couped, and then both old and new clintid will be tied to the same devicetoken. When the group tweets, the apns are sent on the basis that clenid found devicetoken, and then both old and new clintid send a data that leads the client to receive two data。
Which is better in performance, which is the tcp approach and which is the scenario
Tcp is a long link. It's bigger, it's better
Tcp doesn't support toapp's grouping
The group pushed toapp by http because there was only one request
8, the ios platform successfully received, the service code pushed to app, but failed to receive it, and returned to appidnousers wrong
See if ios is added to the phonetypelist in the code. To change to add (“ios”)
9. Solutions for failure of ios signatures:
Problem description: the applicatioNo, i'm not.
The solution: to replace the bundleidentifier with your own id, which means you should fill out the application that you have applied for in your certificate。
How do you get access to devicetoken under a production certificate
The production certificate is not available on-line in xcodé, and first the application is to be packed out, installed on a mobile phone, then your settings are selected in the xcodé origanizer->device, and then the logs are printed in the consloe, and devicetoken and clintid are printed。
11, os development certificate and production certificate packing teaching cheng
Certificate of production environment: http://wenku. Baidu. Com/lInk? Url=yhxg022xh brvrrzxutndz0anevcm6w9218tivzx phntz2t1k9y d-g7jm9-jnfacwbyxcjf6eqhbmvexlbvmlfelxtb5-kuf2il4qae
2. Certificate of development environment: http://wenku. Baidu. Com/view/6ddcd27192e453666f505. HTML
With regard to the notification function of os8:
1. If compiled using ios8sdk, the new registerforremotenotifications/registerusernotificationsettings interface is required, otherwise access to devicetoken is not possible
2. If you use pre-ios8 sdk to compile the interface, you need not change it, just use the old registerforremote notifications interface
13. After receipt of the notice, click on the notice box to make the notice disappear in the notice box。
This notice, which would not have been cleared, would have required the client to write his own code to clear it. Http://www. Cocoachina. Com/ask/questions/show/99491
