将新的iOS应用程序版本更新到App Store [英] Update new iOS Application version to App Store

查看:118
本文介绍了将新的iOS应用程序版本更新到App Store的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

如何将我在应用商店中的应用更新为新版本?

之前,我已成功将我的应用程序提供给应用程序商店.那是起点.但是已经有一段时间了,我已经更新了我的应用程序,并希望提供一个新版本.由于准备应用程序的错误步骤可能会花费一些时间,因此我想采取一些特定的步骤,以便在Apple应用程序商店中提供更新的发行版.

解决方案

摘要

将新版本的iPhone应用程序发布到Apple App Store的过程需要很多步骤,但是并不需要所有步骤,具体取决于证书是否为最新版本,内部版本是否为必需版本(如果您有).所需设备等的屏幕截图.以下是将新版本放入Apple应用商店中可能需要执行的步骤示例.

步骤

1.版本控制和签名

在XCode应用程序中,更新应用程序的版本.还要检查是否有有效的配置文件.在此示例中,配置文件已过期,因此将需要其他步骤.如果您有有效的配置文件,请跳过(冗长的)步骤2.

2.更新配置文件

如果您有有效的个人资料,请跳过此步骤.

此过程不使用XCode应用程序的自动管理签名功能.仅当您拥有物理的,注册的Apple设备(我没有)时,自动签名才有效.因此,自动签名可能会更容易,但在此示例中未使用自动签名.

2a.添加签名证书

在这里,我们看到没有有效的签名证书,因此创建了一个证书并将其与Apple ID关联.

2b.使用`developer.apple.com`

管理证书通过使用Apple开发人员网站,我们看到旧的配置文件已过期,并且我们还看到了新的发行证书.我们为应用商店创建一个新的分发配置文件,并生成一个新的配置文件,然后将其下载.

2c.将新的Provisioning Profile导入XCode

在Apple开发人员网站上创建新的Provisioning配置文件后,我们将新的配置文件导入XCode.如果没有签名证书存在问题,则可能需要选择(项目)->生成设置,然后为PROVISIONING_PROFILE进行设置,并对其进行调整.或先打开再关闭,然后自动管理签名.

3.构建并上传应用程序

在这里,我们使用通用设备构建应用程序,使用第2步中的配置文件(或更早的有效配置文件)进行归档和上传.

我们还必须等待自动处理完成.Apple会生成并发送一封电子邮件.

4.准备提交申请

在这里,我们分配一个商店版本"编号,分配在第3步中上传的构建文件,并再次确认应用程序元数据.

元数据包括应用程序的屏幕截图,Apple要求表示某些屏幕尺寸.这个答案不会探讨与苹果因要求不同的屏幕截图分辨率而给开发人员造成额外负担的情况有关的挑战.相反,将包含对另一篇文章的引用:一旦元数据完成,就可以将版本提交给Apple批准.我认为,这个过程需要一个真实的人,而且至少要花一整夜,甚至更长的时间.该答案不会解决针对特定应用程序的审核过程,但是即使新版本没有任何重大改变,您仍可能会被要求更改提交内容甚至应用程序中的内容.>

How to update my app in app-store to a newer version?

Earlier, I successfully offered my app into the app-store. That's the starting point. But it's been a while, I've updated my app, and would like to offer a new release. Since a misstep in preparing the app can take a bit of time, I'd like to have the specific steps required to offer an updated release on the Apple app store.

解决方案

Summary

The process of releasing a new version of an iPhone app to the Apple app store requires quite a number of steps, but not all the steps will be required, depending on whether certificates are up to date, builds are targeting required versions, if you have screen shots for the required devices, etc. Below is an example of the steps you might need to execute to put a new version into the Apple app store.

Steps

1. Versioning and Signing

Within the XCode application, update the version of your application. Also check to see that there is a valid provisioning profile. In this example, the profile is expired, so additional steps will be required. If you have a valid profile, skip the (lengthy) step 2.

2. Updating Provisioning Profile

Skip this step if you have a valid profile.

This process does not use the Automatically manage signing feature of the XCode application. Automatic signing only works if you have a physical, registered Apple device, which I do not have. So automatic signing might be easier, but is not used here in this example.

2a. Add signing certification

Here we see there are no valid signing certificates, so one is created and associated with the apple ID.

2b. Manage certificates using `developer.apple.com`

By using the Apple developer web site, we see that an old provisioning profile is expired and we also see our new distribution cert is available. We create a new distribution profile for the app store and generate a new provisioning profile, then download it.

2c. Import the new Provisioning Profile into XCode

After the creation of the new Provisioning profile on the Apple developer web site, we import the new profile into XCode. If there is a problem with no signing certificate, you might need to select (project) -- > Build Settings and searh for PROVISIONING_PROFILE and tweak that. Or turn on, then off automatically manage signing.

3. Build and Upload the Application

Here we build the application using a generic device, archive, and upload using the provisioning profile from step 2, or an earlier valid provisioning profile.

We also must wait for the automated processing to complete. An email is generated and sent by Apple.

4. Prepare Application Submission

This is where we assign a `Store Version` number, assign the build file we uploaded in step 3, and reaffirm the application meta data.

The meta data includes screen shots of the application, and Apple requires that certain screen dimensions are represented. This answer will not explore the challenges associated with the case where Apple creates an additional burden on the developer by requiring different screen shot resolutions. Instead, an reference to another post will be included: Submit iOS build update without re-uploading screen-shots and app-previews . My conclusion for screen shots is that you can often request (through Media Manager), that screen shots you've uploaded be used on various other devices, but when new hardware is released, you'll probably need to generate new screen shots manually.

Once the meta data is complete, the version can be submitted to Apple for approval. This process requires a real person, I think, and has taken at least over night, if not longer. This answer will not address the application-specific review process, but even though the new version didn't change anything significant, you may be asked to alter things in your submission or even within your app.

这篇关于将新的iOS应用程序版本更新到App Store的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆