"Reading notes" ios-release your App

One, add icon

Your app's standard icon on the iphone home screen (icon.png) is a square of 57 pixels *57 pixels, png format, cannot have transparency effect or layer, 72DPI. In addition, you can provide a high-resolution icon in the same format as a 114-pixel *114 pixel ([ Email protected]). This icon will come in handy when the user's device is a retina screen. If you are developing an ipad app, the size of the Home screen icon (icon~ipad.png) should be 72 pixels *72 pixels. If you're developing a general-purpose program that needs to run on both the iphone and ipad, you'll need to provide the three-size icons mentioned above.

In general, every picture resource in the app is prepared for two different versions: a standard resolution picture and a high-resolution picture, a high-resolution chart counting table and a display on the retina screen.

These two pictures have a certain naming convention: the name of the standard resolution picture is: "< file >< device descriptor >.< suffix >", the name of the high-resolution picture is: "< file >@2x< Device descriptor >.< suffix .

The < file > and < suffix names in the picture name > two parts, the file name and the suffix name in the usual sense. < device descriptor > optional, if any, must be "~ipad" or "\~iphone". If you want your app to use a different version of the image on your iphone and ipad, you can specify it with this device descriptor.

Second, add the boot image

Adding a boot image to your app is one of the "little tricks" that iOS devices are prepared for you. When the app starts, the splash image is displayed first to the user, until the app starts to complete the real UI interface. That is, the system will display the app's boot image during the loading of the app, avoiding the display of a blank screen to the user at load time.

Most boot images are very simple, it doesn't matter, because the start picture is just to tell the user that your app starts very quickly. If you use a startup image as a startup page, it will cause you to interrupt their feelings and they will complain about why you wasted their time giving them a meaningless interface instead of launching the app immediately. If you use the boot image correctly, the user will feel that you are starting your application as soon as possible and try your best to give the user the most experience.

Third, compile and sign

Different profiles are used for different purposes, the profiles published by Ad Hoc are used for Alpha and beta testing, and the App Store release profile is used to publish your app's final version to the itunes App Store.

The version generated by Ad hoc mode is used to publish your app outside of your development environment and can be published to your beta testers or enterprise internal use. As with the iOS devices that we previously registered for development, you need to register all of the devices that are running the ad hoc version of your app. You can register up to 100 devices per year in iOS Provisioning portal, which is a hard rule, and if you have exceeded 100, you will not be able to register new devices even if you delete the registered devices.

Four, submit to app Store

A SKU is an identifier that contains only letters and numbers that uniquely identifies your app. Note that the SKU will not be changed later, even if the new binary package (or version) of the app is uploaded, theoretically you can choose any string, but it's best to describe your app well and be independent of the specific version.

1, version number, value must be 1.0 or above, submission to App Store less than 1.0 is also one of the reasons the audit team rejected your app.

2, if your app uses a third-party online service, you must have an account to use all features, you must provide a test username and password here. Otherwise, the audit team will also reject your app.

3, you need to upload an 512*512 pixel icon for your app so that it appears on itunes and at least WFNYG app. Show in the App Store.

Five, the reason why the audit was rejected.

1, the audit team rejects applications that have a version number less than 1.0, or that are labeled "Beta", "Alpha".

2, the applied 57 pixel *57 pixel icon must be exactly the same as the 512 pixel *512 pixel icon. In addition, if you plan to release a free "Lite" version and a "Pro" version of the charge, then the icons for both apps must be different.

3, the use of Apple's image resources in your application, compared to the standard, iOS device pictures, etc., will be a reason for the audit does not pass.

4, apps published to the App store don't allow dynamic connections to private or third-party libraries, which can easily cause Apple to reject your app. However, using a static link library is still a gray area, and generally no problem.

5, another reason to reject you is that the functionality of your app and system built-in apps is duplicated, and apps that extend your Web browser are often blamed. Other similar examples are the application of email clients and music player classes.

6, if your app uses a tabular view, but the way cells are manipulated in table view editing mode does not conform to specifications, Apple will reject your app. For example, you cannot deselect a cell after it has been selected.

7, no detection of network status or improper handling of scenarios where the network cannot be connected (and notifying users) is another common reason for rejection.

8, if your application requires a large number of network transmissions, you need to ensure that these transmissions do not go through the mobile cellular network. If your app is heavily networked over a mobile cellular network, your app will be rejected by the audit team. If your app does do that, you should disable or restrict data transfer when your device switches to a cellular network.

9, when the user clicks the different use text input box, your application should eject the corresponding keyboard. Popping up a non-corresponding keyboard is often a reason for the audit team to reject your app.

10, Apple will test your app one by one from the smallest version you specify to the latest version of the iOS system. If the audit team finds that even some of your apps are not working properly on some versions, they will often reject your app. Unfortunately, they almost never tell you which version of iOS you are having problems with. This can lead to a tragedy, that is, if you are not testing on the iOS version where the team has found the problem, you will not be able to pay attention to the problems they find.

Reference "iOS Programming Guide"

"Reading notes" ios-release your App