Invalid Binary 的解決方案

今天看了很多關於Invalid Binary的問題的解決方案，有什麼icons圖片問題的

、有armv6的問題，還有說是認證的問題，這些都有可能，但一大批ios資深

開發人員這種低級的問題應該不會犯。

據外媒9to5mac報道，蘋果已正式宣布，不再接受訪問iOS裝置UDID的應用申請或應用程式更新，該規定將於今年5月1日起開始實施。

蘋果建議開發人員轉用由iOS 6提供的Vender和Advertising Identifier系統，該廣告識識別系統是iOS裝置專有的非私人識別系統，與

UDID的一個重要區別就是，不會像UDID系統一樣附帶私人資訊，允許開發人員訪問。詳情參考UIDevice
Class Reference。

另外，如果你的應用不支援iOS裝置的視網膜顯示屏和iPhone5的螢幕尺寸，也不得上架App Store。詳情參考iOS
Human Interface Guideline。

然後結合itunes反饋的錯誤原因

Dear developer,

We have discovered one or more issues with your recent delivery for "＊＊＊＊ iPhone版". To process your delivery, the following issues must be corrected:

Non-public API usage:

• Apps are not permitted to access the UDID and must not use the uniqueIdentifier method of UIDevice. Please update your apps and servers to associate users with the
  Vendor or Advertising identifiers introduced in iOS 6.

If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library
that was included with your app. If so, they must be removed.

If you think this message was sent in error and that you have only used Apple-published APIs in accordance with the guidelines, send the app's nine-digit Apple ID, along with detailed information about why you believe the above APIs were incorrectly flagged,
to appreview@apple.com. For further information, visit the Technical
Support Information page.

Once these issues have been corrected, go to the Version Details page and click "Ready to Upload Binary." Continue through the submission process until the app status is "Waiting for Upload." You can then deliver the corrected binary.

Regards,

The App Store team

就是因為UDID的問題。

那什麼地方有UDID呢，那就要看你的應用裡面有沒有靜態庫.a檔案，如百度地圖和友盟等都內嵌 .a檔案

讓我來黑一下ios版百度地圖API吧

百度作為一個大公司反應很產品真很讓人吐槽,難道沒看到蘋果要禁用UDID了嗎？

更新版本實在是太慢了。現在看到的版本還是去年10月份發的。

解決方案就是刪除百度地圖，友盟的內嵌然後上傳成功了。如果你遇到同樣的問題，可以以這種方式試一下，應該能上傳了。如果不想去掉那就等待老古董出新版本吧