I took over A project that was in the process of migration: Company A did it, and then another company did the new version (most of it was to complete the code and make A big adjustment to the UI), and I took over the unfinished project of migration… One word, pit, two words, pit; Enough teasing.
Scenario: Let me send two test packages. The bundle identifier used by the two IPA packages is com.abcd. CCC (for example). Result: enter the application prompts version update, click confirm and after installation, click to update the current application is not closed, back to the main page, see the new out an application in the current application in the circle (ing) loaded, when the download is complete, the application of new disappear, you will find that the original application really has been upgraded, but did not appear in the current application of the new version mark;
Do not know the description is clear, I should encounter this problem in very few, because I baidu a lot, and did not see this kind of problem.
I found that the bundle name and the bundle display name in the plist file were inconsistent. However, I felt that the inconsistency did not cause such a problem. Finally, I asked the person responsible for the upgrade. I asked him to show me the install.plist file for the ITMS-Services distribution app. When I opened it, I immediately thought I found the problem. The bundle-identifier in it says com.dddd.aaa(for example), which is different from mine. This is because the upgrade was always made by the personnel of the third party company, and the Bundle identifier is inconsistent with this one. Modify it to match the bundle identifier you use for packaging.
Result: Clicking upgrade to install the current app will close immediately, and the new version logo will appear in the lower left corner of the current app after the current app swivel (Loading ing) is installed.