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
When providing a custom sign function to the windows config section you have the option to set a resultOutputPath which is then supposed to be copied over the original file by electron-builder. However, where the actual sign function is called the object is passed using the spread operator which means you are modifying a copy of the context instead of the context itself. This then means that you never have a value for resultOutputPath set where the renaming is supposed to happen.
Minimal repo:
win: {
signingHashAlgorithms: ['sha256'],
sign: async (context) => {
// This should cause a failure when copying the file but it does not
context.resultOutputPath = 'foo';
},
target: ['nsis'],
},
The text was updated successfully, but these errors were encountered:
When providing a custom sign function to the windows config section you have the option to set a
resultOutputPath
which is then supposed to be copied over the original file by electron-builder. However, where the actual sign function is called the object is passed using the spread operator which means you are modifying a copy of the context instead of the context itself. This then means that you never have a value forresultOutputPath
set where the renaming is supposed to happen.Minimal repo:
The text was updated successfully, but these errors were encountered: