iOS 上架－ IPA打包上传遇到问题记录

问题一：



解决方法：

参考：参考http://stackoverflow.com/questions/18976412/launch-screens-supporting-ios6-and-ios7-forced-to-splash-screen

LaunchImage没有适配 Default-568h 的图片 ，按照格式要求PS出所有的图片，在讲其放在 Assets.xcassets 对应的位置上！这个很重要，图片位置和尺寸一定要对！

以下是一些图片对应的像素大小。

Default.png (320x480)

Default@2x.png (640x960)

Default@2x~ipad.png (2048x1496)

Default~ipad.png (768x1004)

Default1024x768.png (1024x768)

Default1024x768@2x.png (2048x1536)

Default-568h@2x.png (640x1136)

Default768x1024.png (768x1024)

Default768x1024@2x.png (1536x2048)

Default-Landscape~ipad.png (1024x748)

Default-Portrait@2x~ipad.png (1536x2048)

如果不知道怎么对应位置，可以这样操作（吸取了多次放错位置的经验教训，都是泪啊。）

如图，建一个系统自带的LaunchImage图片，由于我们只需要适配iphone，所以不需要的勾都去掉了。



如图，当你点击图片位置时，可以看到这边要求放的尺寸。根据提供的尺寸对照，很明显可以发现 就是这张图片没适配所以出错了。(对!没错!就是这个!以后一定记得做适配！！)



然后重新编译提交就可以过了。

问题二：



解决方法：

使用 product- archive 后，不直接上传iTunes connect，而是 点export到本地，在使用 Xcode 自带工具–application loader 上传 ，就解决了。。。。

application loader 一般都有安装，可以直接点击xcode- open develop tool 就可以找到了

问题三：



App转移后出现的问题 ，推送证书更改问题 。实际直接上传就行了。不用管，对审核没影响。再下一个版本就不会有这个警告了

解决方法：https://developer.apple.com/library/ios/qa/qa1726/_index.html

在itunes connect中构建版本的时候选择你最后一次上传的版本号，build号，跟你上传的app两个一致就没问题了，没出现一致的就等会刷新看看，只要上传的app没出现error就行。

以下附上原文.

From Apple’s Q & A

Resolving the Potential Loss of Keychain Access warning

Potential Loss of Keychain Access. The previous version of software

has an application-identifier value of ‘A1B2C3D4E5.com.company.app’

and the new version of software being submitted has an

application-identifier of ‘5E4D3C2B1A.com.company.app’. This will

result in a loss of keychain access.

Note: This is a warning, not an error. You have the option of

proceeding with the submission regardless of this warning, however

this document should be used to determine whether you can safely

ignore it. This warning indicates that the App ID prefix of the

pending submission differs from the App ID prefix of the live app in

the app store.

Important: The only apps that can safely ignore this warning are those

that do not use technologies that rely on the App ID prefix, like

keychain access, Handoff, and UIPasteboard sharing.

Note: Apps that are migrating their App ID from an arbitrary Bundle

Seed ID to their more-modern Team ID should expect this warning, and

proceed with the submission.

For apps that do utilize technologies that rely on the App ID prefix,

this warning should not be ignored. The Potential Loss of Keychain

Access warning is an indication that the app was code signed with the

wrong provisioning profile.

To resolve the problem:

You must locate or re-create a provisioning profile that uses the correct App ID prefix on the Certs IDs & Profiles website.

Click Edit on the profile to be certain the prefix is correct.

Click Download and save the profile to disk.

Optionally double check the App ID Prefix on the downloaded profile using the Terminal command in: How do I check the entitlements

associated to my Provisioning Profile?

Drag the profile onto the Xcode icon on your Dock to install it.

Re-submit the app and code sign it with the newly restored profile that is associated to the right prefix.