2. The problem may be the certificate, because iOS push has a development certificate and a production certificate. Using Xcode to run on a real machine is definitely a development environment. After packing the ipa bag, you can't get a push. It is very likely that the ipa package is packaged and tested with the production certificate, so choose the last one when packaging and selecting the publishing platform.
Regardless of whether it is an independent developer or an App operator, there is no doubt that message push is the best channel in App operation. If used properly, it can help developers achieve user retention more efficiently. Now, Wiki Rabbit can help you solve the signing problem of enterprise certificates.
The version selected by iOS enterprise signature is very important. According to the stability of certificates, corporate signatures can be divided into three types: independent corporate signatures, stable corporate signatures and * * * exclusive corporate signatures. Many small partners who just entered the signature market will choose the cheapest * * * to enjoy the signature. The stability is poor, and the signature is often dropped. In fact, this version is not recommended to everyone in the official beta stage of APP. If it is a pre-test of the APP, it is optional. Those who pursue high stability can choose the independent version of enterprise signature, and those who pursue cost performance can choose the stable version of enterprise signature.
Of course, we should know that the stability of each version of enterprise signature is relative. At present, there is no signature that will never be cancelled in the market, but how to minimize the frequency of cancellation by means, such as the control of download volume, the classified management of APP, and the way of keeping account books, all affect the stability of enterprise signatures.