ASAR integrity corrupt in v19

[UndefinedOffset]

Preflight Checklist

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

• Electron Packager Version:
  • 19.0.2
• Electron Version:
  • 40.1.0
• Operating System:
  • Windows 11
• Last Known Working Electron Packager version::
  • 18.4.4

Expected Behavior

Asar integrity resource embeded into the application should be a json payload i.e

[{"file":"resources\\app.asar","alg":"SHA256","value":"..."}]

Actual Behavior

Integrity generated ends up being completely corrupt when viewed with Resource Hacker there is a list of files at the top, then the json payload that should be present then a bunch of corrupt data. This results in electron not launching with an error "Invalid integrity config: NOT a valid JSON.".

To Reproduce

Package any Electron app that would have an asar file with the fuse flipped to ensure asar integrity, the packaged application will not launch on windows stating the integrity is invalid. When looking in Resource Hacker the integrity resource will be corrupt and not just a json string.

[welcome]

👋 Thanks for opening your first issue here! If you have a question about using Electron Packager, read the support docs. If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. Development and issue triage is community-driven, so please be patient and we will get back to you as soon as we can.

To help make it easier for us to investigate your issue, please follow the contributing guidelines.