One, add icon
The standard icon (Icon.png) of your app on the iPhone home screen is a 57px*57px square, PNG format, no transparency or layers, 72DPI. In addition, you can also provide a similar format 114px*114px high resolution icon ([email protected]). This icon will come in handy when the user's device is a Retina screen. If you are developing an application on an iPad, the size of the home screen icon (Icon~ipad.png) should be 72px*72px. If you are developing a general-purpose program that needs to run on both the iPhone and iPad, then you need to provide the icons in the three sizes mentioned above.
In general, each image resource in the application should be prepared with two versions of different sizes: a standard resolution image and a high-resolution image, and a high-resolution image inventory table and displayed on the Retina screen.
These two pictures have certain naming rules: the name of the standard resolution picture is: "<file><device descriptor>.<suffix>", and the name of the high-resolution picture is: "<file>@2x<device descriptor>.<suffix>.
The two parts of <file> and <suffix name> in the image name are the file name and suffix name in the usual sense. <device descriptor> is optional, if any, it must be "~ipad" or "\~iphone". If you want your application to use different versions of images on iPhone and iPad, you can use this device descriptor.
Second, add a startup image
Adding a splash image to your app is one of those "little tricks" that iOS devices do for you. When the application starts, the startup image will be displayed to the user first, and the real UI interface will not be displayed until the application startup is completed. That is to say, the system will display the startup image of the application during the loading of the application, so as to avoid displaying a blank screen to the user during loading.
Most launch images are simple, and that's okay, because the launch image is just there to tell the user that your app launches very quickly. If you use the splash image as the splash page, it will give users the feeling that you are interrupting them, and they will complain why you are wasting their time showing them a pointless interface instead of launching the app right away. If you use the splash image correctly, the user will feel that you are launching your app as soon as possible, doing your best to give the user the best experience.
Third, compile and sign
Different description files are used for different purposes, the description files published by Ad Hoc are used for Alpha and Beta testing, and the description files published by the App Store are used to publish the final version of your app to the iTunes App Store.
The version generated by the Ad Hoc method is used to publish your application outside your development environment, which can be released to your beta testers or used within the enterprise. As with the iOS devices we registered earlier for development, you need to register all those devices that will run the Ad hoc version of your app. In the iOS Provisioning Portal, you can register up to 100 devices per year. This is a hard rule. If you exceed 100, you cannot register new devices even if you delete those already registered devices.
Fourth, submit to the App Store
A SKU is an alphanumeric-only identifier that uniquely identifies your app. It should be noted that the SKU will not be changed in the future, even if a new binary package (or version) of the application is uploaded, in theory you can choose any string, however, it is best to describe your application well and Regardless of the specific version.
1. The version number, the value must be 1.0 or above. Submitting a version less than 1.0 to the App Store is also one of the reasons for the review team to reject your app.
2. If your app uses a third-party online service, you must have an account to use all functions. You must provide a test user name and password here. Otherwise, the review team will also reject your app.
3. You need to upload a 512*512 pixel icon for your app to display on iTunes, and at least wfnyg app screenshots. Featured in the App Store.
Fifth, the reasons for the rejection of the review.
1. The review team will reject applications whose version numbers are less than 1.0, or those marked as "Beta" or "Alpha".
2，应用的57像素*57像素的图标必须和512像素*512像素的图标完全一样。另外如果你计划发布一个免费的”Lite"版本和收费的“Pro"版本，那么这两个应用的图标必须不一样。
3，在你的应用里面使用苹果的图片资源，比如图标，iOS设备的图片等，都会是审核不通过的一个理由。
4，发布到App Store的应用都不允许动态连接私有的或者第三方库，否则非常容易导致苹果拒绝你的应用。不过，使用静态链接库在目前还是一个灰色地带，一般情况下都 没问题。
5，另一个拒绝你的原因是你的应用和系统内置应用的功能重复，对网页浏览器进行扩展的应用常常受到这样的指责。其他类似的例子是电子邮件客户端和音乐播放器类的应用。
6，如果你的应用使用了表格视图，但是表格视图编辑模式下对单元格进行操作的方法不符合规范，苹果也会拒绝你的应用。比如，选中单元格进行了操作之后无法取消选择。
7，没有对网络状态进行检测或者不能正确处理无法连接网络的情景（并通知用户）是另一个常见的拒绝理由。
8，如果你的应用需要大量的网络传输，你要保证这些传输不通过移动蜂窝网络进行。如果你的应用会通过移动蜂窝网络进行大量的网络传输，审核团队也会拒绝你的应用。如果你的应用的确会那样做，你应该在设备切换到蜂窝移动网络的时候 禁止或者限制数据传输。
9，在用户点击不同用途的文本输入框时，你的应用应该弹出相应的键盘。弹出了不对应的键盘往往也是审核团队拒绝你的应用的一个原因。
10，苹果会从你指定的最小版本到当前最新版本的iOS系统上逐一测试你的应用。如果审核团队发现你的应用中哪怕只有部分功能在某些版本上不能正常工作，他们通常都会拒绝你的应用。不幸的是，他们几乎从来不告诉你是在iOS的哪个版本上出现的问题。这有可能导致一个悲剧，那就是如果你不是在审核团队发现问题的那个iOS版本上测试，你就重视不了他们发现的问题。
参考资料《iOS编程指南》