@RanVaknin Is there any way to get this assigned a higher priority?

While there is a workaround available it's not obvious that it needs to be used until something fails in a potentially catastrophic way, and teams spend potentially hours investigating.

The documentation pointed to above suggests to a user reading it that the default behaviour is the safe one with retries.

Problem Description:

Once the strategy to merge the files succeeds we know the MachO files we've generated can run on both arm64 and x64. One interesting quirk here is @electron/universal only modifies the temp folder MachO files. It doesn't touch the arm64 folder. That becomes a problem when the arm64 folder is compared with the temporary folder. @electron/universal has modified the MachO files in the temp folder. So they should certainly be different from the ones in the arm64 folder.

Solution Description:

This PR ads a set of files that @electron/universal merged, and then checks the results of the compare to specifically check that files other than the merged MachO files are different.

Problem Description:

Once the strategy to merge the files succeeds we know the MachO files we've generated can run on both arm64 and x64. One interesting quirk here is @electron/universal only modifies the temp folder MachO files. It doesn't touch the arm64 folder. That becomes a problem when the arm64 folder is compared with the temporary folder. @electron/universal has modified the MachO files in the temp folder. So they should certainly be different from the ones in the arm64 folder.

Solution Description:

This PR ads a set of files that @electron/universal merged, and then checks the results of the compare to specifically check that files other than the merged MachO files are different.