iOS的APP在不同开发者账号之间进行转换的方法网上写的比较多,实际操作起来也比较快。

可以参考如下链接文档:

https://support.appmachine.com/hc/en-us/articles/360000012284-Transfer-your-app-to-another-iOS-Developer-Account

或者官方的:

https://help.apple.com/app-store-connect/#/deved688524f

但是,后续其实还涉及到更新APP,证书关联以及一系列配置更新的问题。

如果您是首次在开发者帐户下提交应用程序(应用程序转让给您之后),请按照以下步骤完成更新过程。

这里没有进行完整的翻译,可以参考选择性的根据自己APP的支持情况进行操作。

步骤1:创建推送通知证书

A Push Notification Certificate is necessary in order to send push notifications to attendees via your app. In order to create a Push Notification Certificate, follow the steps below.

  1. Navigate to Apple Developer and log in.
     
  2. Click on ‘Certificates, Identifiers & Profiles’.
     
  3. Select ‘Identifiers’, locate your app, and click on the name.
     
  4. Scroll down the page to “Push Notifications” and click ‘Configure’.
     
  5. A pop-up window will appear. Click on ‘Create Certificate’ under Production SSL Certificate.
     
  6. Click ‘Learn More’ under “Upload a Certificate Signing Request” to learn how to create a Certificate Signing Request (CSR) file. Then go back to Apple Developer and click ‘Choose File’.
     
  7. Use Finder to find your CSR file, select it, and click on ‘Open’ in the dialog window. It will now be visible in the browser. Click on ‘Continue’; it will take a moment to show the next window.
     
  8. Click on ‘Continue’; it may take a moment to show the next window.
     
  9. Your certificate is ready for download. Click on ‘Download’.
     
  10. Locate the downloaded file, called “aps.cer”, on your Mac and click on it. It will trigger Keychain Access to open.
     
  11. To find the certificate in Keychain Access, you can use the Search field in the top-right of the dialog window. Type in the Bundle ID of the App ID. You can now confirm that the Push Certificate was correctly created, is valid, and has an associated private key.
     
  12. Next, you will export this certificate and save it as a .P12 file. First, you must unselect it in the list. Click somewhere below the certificate in an empty space in the Keychain Access dialog window.
     
  13. Right-click on the certificate to show the contextual menu. In the menu that appears, select Export: “Apple Push Services…”
     
  14. A dialog box will open. Select a location to save the file. Give it a recognizable name. For example, “appname_pushcert”. Then click ‘Save’.
     
  15. Another dialog will open, asking you to enter a password, which will protect the P12 file. Type in “doubledutch2019” and enter it twice as requested. Click ‘OK’.

     

  16. Next, send the saved P12 file in an email to your DoubleDutch representative. The DoubleDutch App Operations team will upload this to the back-end admin system. You will be notified when you can test Push Notifications on your app.

步骤2:创建分发证书

A Distribution Certificate identifies your organization within a distribution provisioning profile and allows you to submit your app to the store.

IMPORTANT: you will only need to create one Distribution Certificate for your Developer Account, even if you have multiple apps.

To create a Distribution Certificate:

  1. Log in to Apple Developer.
     
  2. Click on ‘Certificates, Identifiers & Profiles’.
     
  3. The next screen should default to the “Certificates” section.
     
  4. Click on the ‘+’ button to add a new certificate.
     
  5. Select ‘iOS Distribution (App Store and Ad Hoc)’ from the Software options, then click ‘Continue’.
     
  6. Click ‘Continue’ again.
     
  7. Click ‘Choose File’ and select the CSR file you previously created. Then click ‘Continue’.
     
  8. Click the ‘Download’ button to download a .cer file.
     
  9. Double-click the .cer file to install it in Keychain Access.
     

If you encounter any issues during the app distribution process, a DoubleDutch representative may ask you to send a P12 version of your distribution certificate. Here are the steps to create the P12 file:

  1. Go to Keychain Access, and search for the distribution certificate.
  2. Next, you will export this certificate and save it as a .P12 file. First, you must unselect it in the list. Click somewhere below the certificate in an empty space in the Keychain Access dialog window.
  3. Right-click on the certificate to show the contextual menu. In the menu that appears, select Export: “Apple Push Services…”
  4. A dialog box will open. Select a location to save the file. Give it a recognizable name. For example, “appname_distrocert”. Then click ‘Save’.
  5. Another dialog will open, asking you to enter a password, which will protect the P12 file. Type in “doubledutch2019” and enter it twice as requested. Click ‘OK’.
  6. Next, another dialog will open; input your computer password and click ‘Allow’.
  7. Next, send the saved P12 file in an email to your DoubleDutch representative. The DoubleDutch App Operations team will upload this to the back-end admin system.

步骤3:创建配置文件

Provisioning Profiles are needed to define how and to which devices your app will be distributed. Without a Provisioning Profile, you cannot distribute an app through the App Store, or through your own internal distribution method.

  1. Go to Apple Developer and log in with your credentials.
     
  2. Click on ‘Certificates, Identifiers & Profiles’.
     
  3. Click on the ‘Profiles’ section. Then click on the ‘+’ next to the “Profiles” title.
     
  4. Select the radio button next to “App Store” underneath the Distribution heading. This is the Provisioning Profile needed in order to be able to upload your app to App Store Connect. Then click on the ‘Continue’ button at the top.

    Note: if you are publishing your app via Enterprise Distribution you will select “In House” instead of “App Store”.

     

  5. Next, you will be asked to select an App ID with which to associate this Provisioning Profile. Click on the drop-down list and select the App ID that belongs to your app. Then click the ‘Continue’ button.

     

  6. Next, you will be asked to select the Distribution Certificate that this Provisioning Profile will be linked to. Most likely, you will have only one. Select that certificate by clicking on the radio button next to it. Then click ‘Continue’.

     

  7. The final step is to give this Provisioning Profile a name. It is best to give it the same name as your app. You can also include today’s date, to document the date of creation. Then click on ‘Generate’.

     

  8. You can then download the generated Provisioning Profile and save it to your desktop.

步骤4:重新协同设计应用

When distributing your iOS app through your own iTunes account you will have to re-codesign the binary file (.ipa).

Downloading the Re-Codesign Package

In order to get started, you will need to download and unzip the DoubleDutch App Operations Re-codesign Package, mentioned in Item 6 of the Prerequisites list.

  1. Go to https://bit.ly/ddrecodesign
  2. Download the re-codesign package file.
  3. Find the ZIP file on your Mac and double-click on it.
  4. It will unpack and create a folder called “recodesign-master”. This folder contains all the tools for re-codesigning.

Note: please make sure you download the latest re-codesign package file since DoubleDutch makes sure it gets updated as needed.

Prerequisites for Successful Re-Codesigning

  1. A Mac computer.
  2. Transporter installed on the Mac. If you don’t have Transporter downloaded you can download it here.
  3. Xcode 10.1 or higher installed on the Mac. If you don’t have Xcode downloaded you can download it here.
  4. Command Line Tools installed on the Mac, compatible with the version of Xcode you have installed.
  5. Your organization’s iOS Production Distribution Certificate, with the associated private key, in your Mac’s Keychain Access.
  6. The Provisioning Profile belonging to this app, with Associated Domains and Push Notifications enabled, downloaded onto your Mac computer.
  7. The re-codesign package, provided by DoubleDutch.
  8. The .ipa (the binary file format of iOS apps) on your Mac. You will have received this from DoubleDutch.

Re-Codesigning your iOS App

 

  1. Open the “codesign” folder where you have the recodesign.sh script and the Terminal window.
  2. Then, drag & drop the recodesign.sh file into the Terminal window. This will display the entire path of the script file.
  3. Then, drag & drop the Provisioning Profile file you downloaded from your Apple Developer account.
  4. Finally, drag & drop the .ipa file you received into the Terminal window.
  5. You will then see the full path of the files; the makeup of the entire command is the script, followed by two “arguments” – the binary file and the Provisioning Profile. If the two arguments are not there, or incorrect, the script will fail.
     
  6. Then hit the ‘Enter/Return’ key. An example of the Terminal output is shown below:
     
  7. When the script is done, you will have a new folder on your Desktop called “Codesign_Output”. The script will automatically open it. This folder will contain the re-codesigned .ipa file and an entitlements.plist file. The latter can be used for troubleshooting, so do not delete it. It might also be useful to take a screenshot of the Terminal output, for reference and/or troubleshooting.

    Note: you will notice that the Bundle ID of the app will be been injected into the file name of the .ipa. The script does this for the sake of documentation and clarity.
     

  8. You can close the open windows and proceed to upload your app to your App Store Connect account.

Final Technical Notes on Re-Codesigning

This app claims two specific entitlements: Apple’s Push Notification Services and Keychain Access. Push Notifications rely on a setting in the Provisioning Profile.

  • Push Notifications Services must be enabled on your Provisioning Profile for re-codesigning to be successful.
  • If Push Notifications are not available in the Provisioning Profile, the script will output the message: “This provisioning profile doesn’t have push entitlement!”
  • Keychain Access is necessary to store the user’s login and password combination so that the user can access the app, after closing and reopening, without re-logging in.

步骤5:应用上传到App Store Connect

After you have re-codesigned your iOS app, you should be able to upload the binary file to your App Store Connect account. If you are uploading the app to your internal app store, see the administrator of your Mobile Application Management System.

You can upload your app to App Store Connect by using the Transporter app on your Mac.

Follow the steps below to upload your app successfully to your App Store Connect account.

  1. Find the Transporter app on your Mac. You can open Spotlight search and type in “transporter”. It will be the top hit.
     
  2. Open the app and log into the app with the credentials you use to log into App Store Connect. Apple may ask you to create an app-specific password during this step. You can find the directions on how to create an app-specific password here.
     
  3. Drag the .ipa file you re-codesigned, from the Codesign_Output folder on your Desktop, to the “Add App” screen of Transporter.
     
  4. Then you will see an overview of the app’s details. Click on ‘Deliver’ to proceed with uploading.
     
  5. The upload process will take a few minutes. Afterward, you can close Transporter.

步骤6:填写App Store Connect应用列表

  1. Log in to App Store Connect.
     
  2. Next, click on the ‘My Apps’ button to go to the overview of your apps.

     

  3. If you don’t have many apps, you should be able to spot your app immediately. Click on it once to be taken to the app listing. If you have many apps, you can use the Search field to find your app.
     
  4. Once you have opened your app’s listing, in the left menu click on the ‘+’ sign next to “Version or Platform”. It will show you another window where you can select iOS or tvOS. Select iOS.

     

  5. Then another window will pop up where you will need to enter the new version number of your app. Use logical numeric order. If your current app is version 1.0, the version you will type in is 1.1. If you had version 1.9 in the App Store, your next version would be 2.0. Then click ‘Create’.

     

  6. Then you will see the new app listing. All the fields are the same as when you first filled in the app listing, except the new field at the top where you can specify what the changes are in this new version. To keep it concise, you can type in “Bug Fixes and Feature Enhancements”.

     

  7. If you have any changes to make to the images, remember to delete the old ones before submitting the app for review. If you need to change the app icon, you must first delete the old one, only then can you upload a new one to the app listing. If desired, you can also change the app name at this time. This can be done by selecting “App Information” in the upper left-hand corner of the app listing in App Store Connect.
     
  8. All other fields can remain the same unless specified by DoubleDutch that changes have been made. After every change you make to the app listing, it is prudent to click on the ‘Save’ button in the top-right.
     
  9. The final step will be to select a new build to associate with this updated app listing. The new .ipa file you uploaded earlier should be available to select by this point in the “Build” section of the app listing. You will see a “+” sign next to the heading. Click on it to open a pop-up window.

    If you do not see the “+” sign, it means that your app is still being processed by Apple’s servers. It should become available within 30 minutes of uploading. You can periodically refresh the app listing page by pressing: CMD + R.

    Note: due to Apple’s web security settings on App Store Connect, it may happen that your session will be closed when you refresh the page. Do not worry; you will be taken back to the login page. Simply log in again, find your app and continue your work where you left off. This is also a reason why it is prudent to save your work frequently.
     

  10. The pop-up window should show your app build, ready to be selected. Click on the radio button next to the build number and then click on ‘Done’.
     
  11. You will be taken back to the main app listing page, click on ‘Save’ in the top-right.
     
  12. Once your new app listing is saved, with all new images, icon, name, description, and new app build attached to the listing, you can click on ‘Submit for Review’ in the top right.
     
  13. The final stage to confirm your submission is to answer two questions about Export Compliance and an Advertising Identifier in the app. You can select ‘No’ for both of the questions, then click on ‘Submit’.
     
  14. You will now be taken back to the app listing, and as a confirmation, you will see that your app has the status “Waiting for Review”.

您已完成应用更新! 这意味着您提交的应用程序已放入Apple审核部门的审核队列中。 通常,与新应用相比,对应用更新的评论花费的时间更少。 但是,这完全取决于Apple及其审查队列。 应用程序更新批准最多可能需要两个星期。 建议在计划应用启动时考虑到这一点。

以上部分内容摘自:

https://customersupport.doubledutch.me/hc/en-us/articles/360009789813-iOS-Updating-an-Existing-App-for-the-First-Time-after-an-App-Transfer

由于部分图片上传失败,所以仅选取了步骤记录。