Problems with manually submitting a MacOS app to the Apple Store

Question

Created Jan ’20

Replies 5

Boosts 0

Views 1.9k

Participants 6

Hello!

I'm trying to submit a Java app to the Apple Mac Store, so I have to do this manually. I could fix 23 of 25 issues but I stuck on the last 2 😉

ERROR ITMS-90230: "Invalid product archive metadata. Error in keyPath [product-metadata.product-identifier]. Please re-build your archive with an up-to-date version of Xcode, and submit again."

ERROR ITMS-90230: "Invalid product archive metadata. Error in keyPath [product-metadata.product-version]. Please re-build your archive with an up-to-date version of Xcode, and submit again."

For both of them I couldn't find anything useful in the net. What does ist mean and how to fix it???

The result is the same in the Transporter app and when uploading manually in the terminal.

Thanks in advance for any hint!

Thomas

Boost

Answer 1

erwe OP

Jun ’20

I am also facing same issues when try to upload the package manually. Any solution you found?

0

Answer 2

clesuch OP

Jun ’20

Hello,

I have the same issue... Any reason, solution found?

0

Answer 3

DTS Engineer OP

Apple

Jun ’20

What tool are you using to you create your installer package?

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

0

Answer 4

crystal-idea OP

Jun ’20

Same problem here when using Transporter. Any ideas? Thanks.

ERROR ITMS-90230: "Invalid product archive metadata. Error in keyPath [product-metadata.product-identifier]. Please re-build your archive with an up-to-date version of Xcode, and submit again."
ERROR ITMS-90230: "Invalid product archive metadata. Error in keyPath [product-metadata.product-version]. Please re-build your archive with an up-to-date version of Xcode, and submit again."

0

Answer 5

DTS Engineer OP

Apple

Jun ’21

I'm also facing the same issue

I’ve helped a number of Java developers with issues like this and my experience is that they are all related to packaging problems. The Mac App Store expects the apps you submit to be… well… Mac apps, and a lot of Java packaging techniques create something that kinda looks like a Mac app but, once you scratch the surface, is very different from an app generated by Xcode.

The number one problem is that these packages tend to use a shell script as the main executable. This is a bad idea for all sorts of reasons, but it’s definitely not acceptable to the Mac App Store.

Beyond that I don’t have any specific hints. My general advice is:

Use Xcode to build a dummy app that has the same App ID as your Java app.
Run that through the validation process. That should work, but if it doesn’t then you know the issue is unrelated to Java.
Once you get that working, compare the packaging in your working native app with your non-working Java app and look for obvious problems.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1