-
Notifications
You must be signed in to change notification settings - Fork 998
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
[Bug]: #7573
Comments
This issue needs more information before it can be addressed. In particular, the reporter needs to provide a minimal sample app that demonstrates the issue. If no sample app is provided within 15 days, the issue will be closed. |
The best example is to create a JavaScript project using vite then install capacitor dependencies include android dependency then build it and run it using bun you will found that the cli of android file in particular run.js file will bring an error of unidentified and used EACESS. |
can you provide the sample app? |
I have created a new repo named BunJSCapactiorJS |
You didn't link the app, is it this one https://github.com/IsaacPere/BunJSCapactiorJS ? I've tested it and it's working fine on my computer (macbook with macOS Sonoma 14.5) I ran:
I had bun 1.1.3 installed, also updated to latest (1.1.21) and also worked fine. because you mean bun, right? in the description you mentioned bunjs, which is a 4 year old Chinese package. You also mention
|
✔ Copying web assets from dist to android/app/src/main/assets/public in 14.42ms I gotten the messages but I forgot to tell you that I am using kali linux |
Capacitor Version
bun run android
not function defined eacess.....
Other API Details
Platforms Affected
Current Behavior
I am having an issues with capacitor cli that aid in running android platform, can you consider to rewrite the entire cli android run.js file and then refactor the initialization of gradle and it running.
Expected Behavior
running smoothly and brazing fast in bun and node
Project Reproduction
capactor/cli/android/dist/run.js
Additional Information
No response
The text was updated successfully, but these errors were encountered: