You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?!
The text was updated successfully, but these errors were encountered:
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:
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?!
The text was updated successfully, but these errors were encountered: