Issues with @electron/osx-sign version 1.3.1 causing validation errors (90230, 90264)

[Jeepeng]

Description

I encountered multiple validation errors when uploading my pkg file using Transporter after upgrading @electron/osx-sign from version 1.3.0 to 1.3.1. Reverting back to version 1.3.0 resolves these issues. The errors are as follows:

1. 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: 244a41aa-94ec-40ce-840b-35b864e673c0)

2. 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: 72d99a9e-9d4c-49f2-a6e9-a86a8b7b9261)

3. 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: 3ed194c6-6eb7-4455-984f-147c6b679eb6)

Steps to Reproduce

1. Upgrade @electron/osx-sign to version 1.3.1.
2. Sign and make your Electron app for Mac App Store using the following command:

   electron-forge make --arch x64 --platform mas

4. Upload the pkg file using Transporter.
5. Observe the validation errors.

Expected Behavior

The pkg file should pass validation without any errors, as it does with version 1.3.0.

Actual Behavior

Validation errors 90230 and 90264 occur, preventing the pkg file from being uploaded successfully.

Additional Information

• macOS Version: 15.0 Beta (24A5289h)
• Xcode Version: 16.0 beta 3 (16A5202i)
• Electron Version: 31.2.1
• electron-forge: 7.4.0
• Node Version: 20.15.1

This issue seems to be specifically introduced in version 1.3.1 of @electron/osx-sign. Reverting to version 1.3.0 resolves the issue, suggesting a regression or an unintended change in the new version.

Please let me know if you need any further information or logs to help diagnose this issue. Thank you for your assistance!