-
Notifications
You must be signed in to change notification settings - Fork 35
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 dismiss doctor (even if working) #297
Comments
@asleepace could you run |
@lucasbento yeah sure thing! pod --version
1.15.2
bundle exec pod --version
1.14.3 |
@asleepace I had a similar problem and in my case was because I'm in a M1 mac and my terminal was in rosetta mode, while the vscode terminal was in To check that, you can run So when I turned off rosetta mode and updated my gems with |
@RuanAzevedo awesome thanks for the suggestion, will try today! |
Same problem here. I am running a managed Expo project with no custom iOS code (and therefore no need for CocoaPods) and (for now) I don't care about testing it on Android, so I haven't installed an Android Emulator. But the doctor expects this, and cannot be dismissed. Even though the app runs without issue. Expectation: The "doctor" should only warn me about a missing Android Emulator if I try to run the app on Android. And should only warn me about missing CocoaPods if I have code that requires it. |
Description
Found a small bug where the doctor can't seem to find our Cocoapods (we are using a monorepo), but the app is still able to run. As a result we are unable to dismiss the warning. Other than that this tool is amazing and gonna be a game changer for us! 🚀
NOTE: The preview is working
Environment
The text was updated successfully, but these errors were encountered: