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

ádasdasd OP

Jan ’21

I got the same issue.

Sahal OP

Jan ’21

Same here.

Dear Developer,
We identified one or more issues with a recent delivery for your app, "XXXXXXXX" 0.0.44 (0.0.4). Please correct the following issues, then upload again.
ITMS-90000: This bundle is invalid - $message.
Best regards,
The App Store Team

Sang Tran2 OP

Jan ’21

Same issue

halilozel OP

Jan ’21

I'm getting the same error from Turkey

humengchi OP

Jan ’21

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

SpeedySnail OP

Jan ’21

Same issue!

Chikko OP

Jan ’21

Guys, got a solution to whoever still have this issue:

Create a new archive (with a new build version), and distribute it - but this time, remove the check from the "Upload your app's symbols to receive symbolicated reports from Apple".

I can confirm this works for me, app is now being processed.

Thanks to Martin Parker for the tip!

shanksGuo OP

Jan ’21

saaaaaaaaaaaaaaaaaame

Sonney OP

Jan ’21

same here
please fix it!!!!!!

ZZY_hao OP

Jan ’21

untick the "Upload your app's symbols to receive symbolicated reports from Apple" when upload a build to app store connect should help.this is valid

easymovie_zhiheng OP

Jan ’21

same here

cmlsimon OP

Jan ’21

Me too from HK!
Thought it was my problem.
I passed Validation and Distributed to appstore.
The build appears blank in testflight, but after sometime it disappear.
After found this posts, now is Apple’s problem.

Moyck OP

Jan ’21

untick the "Upload your app's symbols to receive symbolicated reports from Apple" is work for me.

thx @Chikko @ZZY_hao

sirplusplus OP

Jan ’21

I had just sent the same build, only changed the build number, and haven't got this error. Seems like Apple has just fixed this issue.

vobic OP

Jan ’21

Same here!