When I first started working on the RN project, there was a bundleID abc, but when I pushed it later, this bundleID seemed to be occupied by the unified allocation and could not be used. After that, I added "168" after the bundleID. "->abc168, there is no problem in running, so I used this bundleID to complete the push of the certificate.
But the push project cannot push the new certificate created by abc168. I thought that just changing the bundleID in General and info.plist would not completely change it, so I tried to key a project with the new bundleID and found that push could be used. . .
Now comes the question:
Copy all the code of the original project to the new project. Which files need to be modified?
How to completely change the bundleID of the original project to a new bundleID (just modifying it in general and info.plist on xcode does not work)?
習慣沉默2017-05-17 10:06:33
Since there was no other idea, the first method was used to solve the problem:
Rebuilt a project with a new bundleID, and then transplanted the code of the previous project. What should be noted here is that if there are third-party libraries in the original project, these libraries need to be reconfigured.
滿天的星座2017-05-17 10:06:33
In addition to certificates and description files, various other things also need to be reconfigured. If you use xcode8, they will be automatically generated; if you use a third party for push, such as Jiguang, the previously uploaded push certificate will also need to be reconfigured; test again later and receive it. It must be that the configuration is not configured properly or the push method is selected incorrectly. For Jiguang, just click Send notification to test it;