Repository navigation
Electron-Builder Incorrectly Uses Host RID for Build #1097
Description
I'm unsure what exactly caused this bug, but the recent 0.5.2 update has broken my current cross-platform build pipeline. It seems like the electron-builder is now always building binaries for the RID of the host system, rather than the RID provided via the CLI args or publish profile. This issue occurs on all platforms; I tested the following scenarios:
- Targeting
win-arm64while onwin-x64 - Targeting
osx-x64while onosx-arm64 - Targeting
linux-x64while onlinux-arm64
Configuration:
- Package Version: 0.5.2
- Electron Version: 42.4.1
- Electron Builder Version: 26.8.1
- Framework: net10.0
- Target: any
Steps to Reproduce:
- Install the latest package version (
0.5.2) - Specify an RID with an architecture different from the host system (e.g.,
win-arm64on awin-x64system) via a publish profile (RuntimeIdentifier) - Build the project using the same RID (e.g.,
dotnet publish MyProject.csproj -c Release -r win-arm64 -p:PublishProfile=win-arm64) - Investigate/test the build artifacts; the
electron-builderoutput will also have the incorrect name (e.g.,linux-arm64-unpackedon alinux-arm64system when targetinglinux-x64for which the folder should be calledlinux-unpackedby default)
Activity
[-]Electron Incorrectly Uses Host RID for Build[/-][+]Electron-Builder Incorrectly Uses Host RID for Build[/+]epsnm commentedon Aug 10, 2026
@AeonSake Adding the architecture to the path occurs when the arch does not match with the default platform architecture.
This is the default behavior of electron-builder (see https://github.com/electron-userland/electron-builder/blob/075efcf2725a733aa25bb115801dee62e85a5594/packages/app-builder-lib/src/platformPackager.ts#L260).
If you change the default arch in electron-builder.json per platform.
If we want to replicate the previous behavior (always match the targeted arch, we can add
-c.$(ElectronPlatform).defaultArch=$(ElectronArch)to enforce the default arch being the dotnet arch)There is another issue here: as we let the electron builder choose the architecture, the cross-compiler chooses the wrong one. You can see it using
--tl:offwhile building.@FlorianRappl can you assign it to me ?
epsnm commentedon Aug 10, 2026
#1098
Merge pull request #1098 from epsitec-sa/bug/#1097
AeonSake commentedon Aug 10, 2026
I'm not talking about the fallback/default architecture. When an RID is explicitly set via
dotnetCLI args, that RID should really be propagated toelectron-builderas it did before. I'd expect the default architecture when, and only when, the RID arg is missing. That would be the behavior I'd expect and that's also howdotnetitself does it. There's also an arg for the architecture itself which should ideally also be supported.-a|--archsets the given architecture and defaults to the host for the platform (basically building an RID from the architecture and host platform). Similarly, there's--osfor the platform only.AeonSake commentedon Aug 10, 2026
It's probably worth mentioning that what I do in my cross-compile pipeline is the documented and recommended approach, based on the Wiki for Package Building and #943 (comment). I'm not sure why the RID argument is still required even though it's specified in the publish profile, but it also never worked without it in builds that involve multiple project dependencies. Regardless, that RID really should be the main identifier for
electron-builderbecause why would you build a .NET binary for a different architecture than the electron shell.Fixes #1097