Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asset validation failed. Invalid product archive. #327

Open
sanjubhambhani opened this issue Jul 17, 2024 · 2 comments
Open

Asset validation failed. Invalid product archive. #327

sanjubhambhani opened this issue Jul 17, 2024 · 2 comments

Comments

@sanjubhambhani
Copy link

sanjubhambhani commented Jul 17, 2024

Node: v20.15.0
Electron: v31.1.0
Electron Forge: v7.4.0

Working on submitting a "mas" build to the Mac App Store. The build is packaged, code-signed and sandboxed correctly. However uploading the pkg file on Transporter for verification returns the following errors:

Asset validation failed (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. (ID: ed4e62c9-8b3a-41f0-ad67-c54c4c479459)

Asset validation failed (90264)
Invalid product archive. The lowest minimum system version in the product definition property list, none, must equal the LSMinimumSystemVersion value, 10.15. (ID: 123ed95f-a48c-44c7-84e4-1a56c7a16203)

Asset validation failed (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. (ID: 363b8f8f-a457-4511-9e04-f1d981719f63)

I have the latest version of Xcode and confirmed the app name, version, build number and build identifier are all correct. They are all appearing in the Info.plist file in the build app as expected.

Anyone having the same issue and/or have a fix?!

@Jeepeng
Copy link

Jeepeng commented Jul 17, 2024

I encountered the same issue, and downgrading to version 1.3.0 worked for me. #328

@sanjubhambhani
Copy link
Author

I encountered the same issue, and downgrading to version 1.3.0 worked for me. #328

appreciate the heads up, was stuck in this for a whole day!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants