Xcode App Submisson ERROR ITMS-90207: "Invalid Bundle
Asked Answered
V

6

10

When I am submitting Application through Xcode Application validation successful but when submit to Appstore Then This error Occur.

ERROR ITMS-90207: "Invalid Bundle. The bundle at 'example.app' does not contain a bundle executable

I also try Application loader Version 3.1 but same error occur. I refer all link like
link 1 link 2 link 3 link 4

enter image description here

Viddah answered 27/10, 2015 at 13:48 Comment(7)
Are you certain the file in the app bundle is executable etc? Check with file.Nureyev
@Nureyev i check all the files in bundle but i could not file executable files. please give some file extension which create this type of problems.Viddah
I don't understand what you are asking.Nureyev
Please see my update comment aboveViddah
So it looks like Apple is correct. You are not creating a valid app bundle. You should look into that, as there is almost certainly error messages you are missing.Nureyev
@ilesh Have you any success in this? I'm banging my head on the desk because of the above error.Relapse
Possible duplicate of Invalid Bundle. The bundle at '.app' does not contain a bundle executableParasitic
G
8

The connection to the info.plist file might be causing the issue. Try changing the bundle id from target and check if it reflects in the plist file and vice-versa. If this doesn't reflects copy your plist file at some other location, remove it from the app and drag and drop again, it will help. This solved my issue, hope it helps.

Gaudreau answered 28/10, 2015 at 6:57 Comment(1)
Changes are reflecting in plist file. But still getting the error. Not able to upload.Relapse
S
11

Please check your info.plist file and add below key if not

<key>CFBundleExecutable</key>
    <string>$(EXECUTABLE_NAME)</string>
Scabies answered 30/10, 2015 at 12:5 Comment(3)
I'm having the same problem but solution above is not working.Relapse
will you plz provide me screen shot of your error.? @Manish VermaScabies
@RahulPatel I solved it. Actually there exists the CFBundleExecutable key in the plist file but my plist contained some characters which made it invalid xml. So after removing invalid characters my app uploaded successfully.Relapse
G
8

The connection to the info.plist file might be causing the issue. Try changing the bundle id from target and check if it reflects in the plist file and vice-versa. If this doesn't reflects copy your plist file at some other location, remove it from the app and drag and drop again, it will help. This solved my issue, hope it helps.

Gaudreau answered 28/10, 2015 at 6:57 Comment(1)
Changes are reflecting in plist file. But still getting the error. Not able to upload.Relapse
L
1

I was dealing with this error since yesterday and when I was about to give up I tried with a different Mac and it worked, the only difference between the OSX was that I updated to Xcode 8.2.1 and the other OSX had 8.2. Hope it helps!

Lubumbashi answered 12/1, 2017 at 15:57 Comment(0)
T
0

I had this issue and was banging my head on the desk for several days. I tried all solutions posted online and nothing worked. For me it ended up being corruption in my 'Bundle display name' (aka CFBundleDisplayName) key in my info plist file. There was a rogue '¿' character that would not get removed when I changed the entry in Xcode (I know this because I tried setting several keys within Xcode). I had to remove the key and re-add it get it fixed. The only way I ever saw this was to open the plist with a text editor. Xcode never rendered the bad character. If you are seeing this issue check you plist file in a text editor for any bad characters.

Tengler answered 19/1, 2016 at 19:57 Comment(0)
P
0

I had the same error during upload, I was pretty sure about the bundle structure is perfect, the executable at the correct place and the Info.plist points to the correct place, contains the correct name, just like the localized versions. I decided to ask for help from the Apple support. After a long process it is turned out that my ~/.itmstransporter folder was corrupt or outdated. After deleted the folder it is re-created automatically and the problem went away.

Phuongphycology answered 1/8, 2017 at 8:14 Comment(0)
S
0

For my case, it was because i moved application loader to another disk. After moving it back to mac os disk, it works fine.

Sawtoothed answered 26/5, 2018 at 21:58 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.