Xcode IOS 주최자 앱 스토어에 제출 "아카이브가 잘못되었습니다"오류가 발생합니다.

Question

Xcode 3에서 4에서 방금 전환했습니다. 주최자에게 아카이브 된 앱을 업로드하려고하면이 오류가 발생했습니다.

아카이브가 유효하지 않습니다. /var/folders/.../app.ipa는하지 않습니다 존재합니다.

iTunes Connect에 로그인 한 후에는 업데이트 할 응용 프로그램을 선택하고 다음을 선택합니다.이 오류가 발생하는 것을 알아 내려고 노력할 위치가 확실하지 않습니다.진단에 유용 할 수있는 모든 것을 남겨두면 알려주세요.감사합니다

Answer 1

괜 찮 아 요, XCode 4 패키지를 설치하면 "Unix Tools"옵션을 선택했는지 확인하십시오.이것은 내 경우에 문제가있었습니다.

Answer 2

나는이 문제에 직면했고, 나는 그것에 대한 해결책을 발견 한 것처럼 보입니다. 올바른 프로비저닝 프로파일이 선택된 것으로 보이지만 그렇지 않을 수도 있습니다.

가능한 프로비저닝 프로파일 목록을 수동으로 탐색하고 올바른 것을 선택하십시오.설정을 자동으로 선택하지 마십시오.

"ID :"- LIST, "현재 일치하는 ..."이라고 말하지 않도록하십시오.수동으로 올바른 것을 선택하십시오.

문제를 해결해야하며 AppStore에 업로드 할 수 있어야합니다.

Answer 3

Xcode Beta 버전을 실행하는 경우, Beta 버전에서 앱을 제출할 수 없으므로이 오류가 발생합니다.이 제한 사항은 읽기 ME 파일 또는 Xcode 다운로드 페이지에서 언급되지 않습니다.앱을 제출하려면 개발자 도구를 제거한 다음 최신 버전 버전을 다시 설치 한 다음 컴퓨터를 다시 시작해야합니다.

제거 할 명령 줄 명령 :

sudo /Developer/Library/uninstall-devtools --mode=all

.

Answer 4

1. xcode 를 종료합니다
2. 텍스트 편집기가있는 파일을 엽니 다. yourproject.xcodeProj / project.pbxproj
3. provisioning_file= 를 포함하는 모든 줄을 삭제합니다.
4. code_sign_identity= 가 포함 된 모든 줄을 삭제하십시오.
5. 저장 및 닫기 Project.PBXProj
6. xcode 에서 프로젝트를 다시 열립니다.
7. 프로젝트를 청소
8. 빌드 설정 창에서 올바른 코드 서명 ID 를 선택하십시오.
9. 재구성

Answer 5

I recently switched to a new MacBook Pro and had XCode 4 installed from a Time Machine drive via the Migration Assistant.

Re-installing XCode 4 with the Unix Tools fixed it.

For some reason those files weren't getting copied across with Migration Assistant.

Answer 6

I had the same issue for both TestFlight and App Store. The solution for me was to archive the app, and in the organizer select "Don't sign" when you try to validate/submit or share (in the case of TestFlight).

Hope this helps.

Answer 7

In my case this has nothing to do with Xcode or the unix tools. Indeed I happend to had too many distribution certificates (Why? I don't know). Deleted all of them but one, code sign with this one, re code sign it while validating and submit it with no errors. I hop this help.

Answer 8

A good way to test is to run the build from the command line. Change to your project folder and run 'xcodebuild' and look carefully at the outputs, especially around the 'codesign' command.

I did this and discovered the following:

architecture armv7 object: /Users/chris/Documents/x/x/build/Release-iphoneos/x.app/x malformed object
object file format invalid or unsuitable

So it isn't a solution, but it at least lets you zero in on what the problem is. Anyway, for me, looks like an architecture config error.

Update - to fix this problem, i replaced the copy of codesign_allocate in my /usr/bin folder with the one in /Developer/somewhere and that fixed it.

Answer 9

I tried most of the ideas above, and they did not work for me, likely because I am using he Appcelerator Titanium platform. I did however delete the Build directory and re-built the product and it passed the validation and I was able to upload the binary to the app store.

Answer 10

The same happened to me. My mistake was I had certificates with similar names (like "Provisioning Profile of Giammy", "Profile for Provisioning of Giammy"...).

Running "Archive" from XCode 4.0 and then "Validate..." from the Organizer I faced the "app.ipa does not exist" issue. The problem was that I selected the wrong certificate from those with similar names. The "Archive" phase worked good but the archive did not pass the validation.

Solution: just picked up the correct provisioning profile in the "Archive" phase.

Lesson learned: check twice the provisioning profile name!

Answer 11

Make sure that you are signing with keys for correct product/bundle ID. If I remember correctly, mixing that up could lead in archiving problems. Also, go to that temp folder and check what IS created. Maybe xCode is creating the IPA under a different name, that could give you a hint.

Answer 12

I solved this same problem by deleting all of the expired signing certificates from my Keychain. Xcode seems to just grab the first one it finds with the given name, regardless of whether it's still valid.

Answer 13

I tried everything including reinstalling xcode4 with unix tools. NOthing works. I assume I shouldnt have to do this as I'm able to submit other apps without issues. I'm just having this issue with a partiular project (coming from xcode3).

I even created a project from scratch, imported all the code over and tried again - failed. so it's not only my project but something in it. So I've started the process of creating a new project, adding some files, then submitting, then rejecting to figure out what's causing it. This is working so far.

update: ok - it has something to do with using CorePlot and linking it in as a library. and voila - found the answer here. Can't submit app with CorePlot using Xcode4 Solution: when submitting select "Don't resign"

Answer 14

I was not able to solve this problem by changing or fixing code signing identities (which should resolve this problem in many cases. Nor did simply reinstalling Xcode. These are the top two solutions as I post this answer.

I found success in uninstalling all the developer tools, and reinstalling from scratch.

Answer 15

Here is how I solved it:

1. Open Keychain and delete all distribution certificates, both from my "login" and from "system".
2. Download the latest Distribution certificate from the Dev Center.
3. Double click the certificate to install on Keychain.
4. On XCode, make sure the certificate name matches on Build Settings.
5. Build for Archive (a Keychain popup should ask for permission to sign the app).
6. Archive (again, Keychain confirmation required).
7. Validate archived app (again, Keychain confirmation will be required).
8. Submit app (one more time, Keychain confirmation will be required).

If you are building for Archive and you don't see any Keychain confirmation dialog, you can stop at that point because submission is not going to work.

Answer 16

i did have this very same issue using xcode_4.2_and_ios_sdk_5_beta__snow_leopard, my working solution.

Install the previous (non-beta) version of Xcode in a different location and work with that version, and that's it, it worked i was able to upload my app to the AppStore without any inconvenience.

regards,

Jorge.

Answer 17

Never try to submit using apps you built using beta SDKs as your base SDK.

I got rid of this problem by uninstalling all developer tools with the below command

sudo /Developer/Library/uninstall-devtools --mode=all

and then restarted my system and installed that latest non-beta version of XCode and non-beta iOS SDK.

Answer 18

Have you been playing around with the ENTITLEMENTS_REQUIRED attribute at /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.3.sdk/SDKSettings.plist (let say to create jailbroken applications)?

In this case, please reset ENTITLEMENTS_REQUIRED to YES.

Answer 19

for xcode 4 I tried every thing but I can t solve this error until install xcode 4.2 for snowleopart

if you cant see your app icon in validation page its can be your xcode have error. download from apple developer page xcode 4.2 and install. its solved. you dont need to uninstall your xcode 4 just download new xcode 4.2 and install. I am very fine now

Answer 20

My solution was:

Open the info.plist file in your project and in product name write your products name instead of $[PRODUCT_NAME]

Answer 21

Had this error in Xcode, but had no such error when using the Application Loader. Get to it via Xcode -> Open Developer Tool -> Application Loader. Very frustrating indeed.