Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to build universal deploy for MacOS 🐛 #173

Open
aswallace opened this issue Jul 15, 2024 · 0 comments
Open

Unable to build universal deploy for MacOS 🐛 #173

aswallace opened this issue Jul 15, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@aswallace
Copy link
Contributor

aswallace commented Jul 15, 2024

Initial notes from Sean:

When Arm64 mac runners became the default for GitHub it seems it broke our desktop deploys to MacOS by having only Arm64 arch compatible executables get output as part of the release process. This can be fixed by changing the build options in the package.json to target x86 as a separate deploy or by building a universal version. However, this is where the trouble really begins. It seems like for some reason the universal and x86 builds that build on GitHub don't actually produce an x86 compatible executable, instead I get this error:

Image

This seems to be an error many others have gotten as well and the routes and various fixes they perform are varied. What is more annoying is it seems the File Upload App does exactly what we do on my working branch but without the error (see here.

Related Issues

Things I tried to so far:

  • Upgrading electron & electron-builder
  • Upgrading electron-builder to a middle ground version like 22
  • Setting mergeAsar to false
  • Setting the node modules included to exclude certain extensions
    (various combos of above, not to say any of these should necessarily be ruled out since it may require the right combo)

Update: Notes from Anya

I eventually narrowed down the issue to DuckDB. When I remove duckdb as a dependency completely (and noop all duckdb functionality) the universal builds work for both arch. I think they've fixed the mac incompatibility issue in 1.0.0 (we're using 0.8.x) BUT when I try to upgrade to 1.0.0 I get a whole bunch of nasty mapbox/node-pre-gyp dependency & webpack errors. Unfortunately, node-pre-gyp is no longer maintained, so I haven't had much luck in finding solutions
Related discussion:

Currently the deployed versions of the desktop app are based on main, but built on their respective chips and manually added to the release.

@SeanLeRoy SeanLeRoy added the bug Something isn't working label Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants