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 use Bubblewrap Build #853

Open
tropicthedev opened this issue May 30, 2024 · 8 comments · May be fixed by #881
Open

Unable to use Bubblewrap Build #853

tropicthedev opened this issue May 30, 2024 · 8 comments · May be fixed by #881

Comments

@tropicthedev
Copy link

Describe the bug
Unable to utilize bubblewrap. While using bubblewrap build I got a cli ERROR spawn EINVAL error.
To Reproduce
Steps to reproduce the behavior:

  1. Install Bubblewrap
  2. run the init command with my website manifest
  3. enter the data to generate the project
  4. run bubblewrap build at the root of the project using the included dependencies

Expected behavior
The CLI to build the android app without issues

Screenshots
If applicable, add screenshots to help explain your problem.
Screenshot 2024-05-29 203653

Additional context
I installed the CLI via NPM and immediately tried to use it but failed

@conorw
Copy link

conorw commented Jun 17, 2024

I encountered this on Windows 11 also.
I was able to workaround this by using a different version of node e.g. 16 instead of 20.13.1

@tropicthedev
Copy link
Author

Will try this

@Andrey-Pavlov
Copy link

I have the same issue
Node v22.3.0

@aibrahim-
Copy link

This is due to a security patch in node, Bubblewrap needs to use { shell: true } when spawning a process: nodejs/node#52554

As a workaround, use older version of node.

@AhmedBaset
Copy link

AhmedBaset commented Aug 13, 2024

This is due to a security patch in node, Bubblewrap needs to use { shell: true } when spawning a process: nodejs/node#52554

shell: true is already utilized. 🤔

@AhmedBaset AhmedBaset linked a pull request Aug 13, 2024 that will close this issue
@AhmedBaset
Copy link

AhmedBaset commented Aug 13, 2024

shell: true is already utilized. 🤔

It turned out to be because of this line:

return await execFilePromise(cmd, args, {env: env, cwd: cwd});

should be fixed by #881

@Henza55
Copy link

Henza55 commented Oct 17, 2024

I used node.js 16 and it worked for me, try downgrading your node.js to an older one.

@AhmedBaset
Copy link

I used node.js 16 and it worked for me, try downgrading your node.js to an older one.

Node 16 is dead. It reached EOL a long time ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants