-
Notifications
You must be signed in to change notification settings - Fork 1k
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: cap run fails to work in a yarn 2+ workspace #6791
Comments
As a workaround, I've just been running the webserver and |
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. |
Here's my example: https://github.com/Jigsaw-Code/outline-sdk/tree/outline-connectivity-app/x/outline-connectivity-app It also seems to happen with android. |
can you provide some steps to reproduce? |
It looks like this issue didn't get the information it needed, so I'll close it for now. If I made a mistake, sorry! I am just a bot. Have a great day! |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Capacitor, please create a new issue and ensure the template is fully filled out. |
Bug Report
Capacitor Version
Platform(s)
Developing on iOS and Android
Running on MacOS, M1 Pro, Ventura 13.5
Current Behavior
I have my capacitor project within a yarn 2+ PnP workspace. I'm running
yarn workspace <package name> cap run ios
and receiving the following error (PII in path redacted):A similar thing happens with Android.
Expected Behavior
There should be a list of targets to load the app on.
Code Reproduction
I've got a WIP project here: https://github.com/Jigsaw-Code/outline-sdk/tree/outline-connectivity-app/x/outline-connectivity-app
Other Technical Details
npm --version
output: I'm using yarn 3.6.1node --version
output: 18.16.1pod --version
output (iOS issues only): 1.12.1Additional Context
I've noticed that we're calling
native-run
with the following:This doesn't seem like it would play very well with PnP? Not sure.
The text was updated successfully, but these errors were encountered: