Which certificates are required before the iOS app is submitted

An app developed and released on someone else's machine, and now iterative updates and development need to be developed and published on a new Mac machine. (Use the same developer account)
Problem:
1. Can I develop and import real machine tests on a new Mac machine, and do I need to import the developer certificate, developer authorization file and development key from someone else's machine to the new Mac machine?
2. Is the program iterative development complete, when the app uploads the Apple App Store, does it need to be released with an older machine to ensure app updates? Can you import the release certificate onto the new machine from the old machine and publish the app with the new machine?
Solution:
Certificate Basics during app development and publishing:
1. Certification (certificate)
Certificate is the qualification of computer development certification, each developer account has a set, divided into two kinds:
1) Developer Certification (development certificate)
Install on the PC to provide permissions: The developer tests the device for real-world testing.
Copies can be generated for multiple computers to be installed;
2) Distribution Certification (release certificate)
Install on your PC to provide permission to publish iOS programs: Developers can make beta and release programs.
Cannot generate a copy, only the computer that configures the certificate can be used; (the copy is introduced in the following keychain)

2. Provisioning profile (Authorization document)
Authorization files are authorized for devices such as ipod Touch, IPad, iphone, the udid of the device and the app ID of the program, even if the authorized device can install or debug the bundle identifier program that corresponds to the app ID recorded in the authorization file.
The developer account will choose the app ID when creating the authorization file (add the app ID in the developer account, select a single) and Udid (add up to 100, multi-select in the developer account under devices).
The authorization file is divided into two types, corresponding to the corresponding certificate use:
1) Developer Provisioning profile (Development authorization file)
When used on a computer with a development certificate or copy, the developer chooses the authorization file to install the program to a device in the authorization file record through the computer, which can be tested on the real machine.
Note: Make sure that the computer has permissions to debug, that is, the development certificate or copy is installed, the bundle identifier of the program in the development tool and the app ID of the selected authorization file are consistent; The udid of the device that connects the debugs is recorded in the selected authorization file.
2) Distribution Provisioning profile (Release authorization file)
The beta and release programs are made on the computer that has the certificate issued (that is, the computer that configures the certificate).
The release is the program file that is published to the App Store, and the developer account chooses the store option when creating the authorization file, choose the app Id, no need to select Udid;
The beta version is the program files that the tester can sync to the device before it is released, select Adhoc when creating the authorization file for the developer account, select the app ID and Udid, and only the selected Udid device may install the program that is made from that authorization file.
3. Keychain (Development key)
If the certificate is successfully installed, keychain will be generated under the certificate, and the copy of the certificate mentioned above is the computer that is configured with the certificate to export keychain (that is. p12 file) to the other machine, so that the other machines get the certificate corresponding permissions. Developer certification can make copies keychain distributed to other computers to be installed so that they can be tested on the real machine.
Note: Distribution certification can only be used by computers that have a certificate configured, so even if the export export keychain is installed on another computer, it is not possible for other computers to have certificate permissions.
The certificate basics above can be seen as a developer certificate that can be imported to a new computer for development and real-world testing, and publishing a certificate is not allowed to import a new computer for app Publishing. So the problem arises. What if the version iteration updates?
For issue 1: By importing the developer certificate, key and development authorization file (import test machine) can be realized with the new computer on the real machine development and testing, in fact, this method solves the problem is how to let others know their own developer account under the premise of allowing more than one Mac machine can also be developed on the real computer test app Suppose now that you know the developer account password you can regenerate the developer certificate, develop the key on your own machine through your developer account, and then use the developer certificate and development authorization file generated by your letter for the real-time development test.
For Issue 2: You cannot update an iteration app on a new computer by importing a certificate; how can I iterate on a new Mac with an app that has to be released iteratively on the old machine? There is no doubt that it is possible to launch an iterative app on a new machine, which involves the upgrade mechanism of the Apple App Store: the same app under the same Development Account the user will automatically be prompted for a new version if the version number is larger than the current version number. So you can create a new publishing certificate on your Mac computer and publish it through this publishing certificate.

Which certificates are required before the iOS app is submitted