ITMS-90000: This bundle is invalid - $message.

Code Signing General App Review App Binary

Created Jan ’21

Replies 481

Boosts 0

Views 65k

Participants 436

Got my binary rejected with the message: ITMS-90000: This bundle is invalid - $message.

There is not more info on this in the rejection email and I am having a hard time understanding what may have happened or how to solve it. Anyone had a similar issue?

Boost

reynecesito OP

Jan ’21

It was working around 16 hours ago, but it suddenly stopped working now

Rich Levy OP

Jan ’21

Same here. Unchecking "Upload your app's symbols to receive symbolicated reports from Apple" didn't solve the problem.

Apple have clearly changed something as I successfully submitted yesterday.

vergiliy OP

Jan ’21

If someone noticed that the problem disappeared or someone found a solution, please write here.

lytuong1900 OP

Jan ’21

same from Vietnam

ZooteeMan OP

Jan ’21

I had the same problem, but, I just waited about 10 minutes, changed the minor build number, then ran through the process and it was accepted this time.

It has to be an intermittent issue on the Apple Back-End.

Kuray OP

Jan ’21

Hey guys,

Here is the temporary solution:

While archiving, it will ask you:
Upload your app's symbols to receive symbolicated reports from Apple

Just UNCHECK this one and you're good to go. At least it works on TestFlight.

Have fun

antonm76 OP

Jan ’21

Same from Russia

plattnum9 OP

Jan ’21

Meeting the same issue.

atiang OP

Jan ’21

same here, reupload same build with previous succeed build (built yesterday) also got invalid bundle message
Unticking "Upload your app's symbols to receive symbolicated reports from Apple" didn't help.

Lenah OP

Jan ’21

Same here. One hour ago tried out the "unchecking symbolicated reports" method and got one version processed. Now another version silently disappeared from TestFlight. Did not even receive an email this time ┑(￣Д ￣)┍

Jueeee OP

Jan ’21

Unchecking "Upload your app's symbols to receive symbolicated reports from Apple" didn't solve the problem！huhu

pavanpowani OP

Jan ’21

I incremented the build number and uploaded again and it worked for me.

RyanOConnell OP

Jan ’21

same here

rtzfghfghfghfghf OP

Jan ’21

Same issue. We did not make any significant changes. It would be great if one of the Apple engineers can replace the placeholder so we can figure out what is wrong.

anehme OP

Jan ’21

same here