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 dismiss doctor (even if working) #297

Open
asleepace opened this issue May 25, 2024 · 5 comments
Open

Unable to dismiss doctor (even if working) #297

asleepace opened this issue May 25, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@asleepace
Copy link

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! 🚀

Example of Issue Doctor Screenshot
Screenshot 2024-05-24 at 6 56 36 PM Screenshot 2024-05-24 at 7 03 31 PM

NOTE: The preview is working

Environment

  • React Native IDE 0.0.14
  • macOS Sonoma 14.4.1
  • VSCode version 1.89.1
  • React Native 0.74.1
  • Cocoapods 1.15.2
  • React 18.3.1
  • Expo 51.0.4
@asleepace asleepace added the bug Something isn't working label May 25, 2024
@lucasbento
Copy link
Collaborator

@asleepace could you run pod --version and afterwards bundle exec pod --version and paste both outputs here?

@asleepace
Copy link
Author

@lucasbento yeah sure thing!

pod --version
1.15.2

bundle exec pod --version
1.14.3

@ruan-azevedo
Copy link

@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 arm64. So I installed cocoapods on my Mac terminal for the arch x86_64 and that's not compatible with arm64.

To check that, you can run uname -m in both terminals (mac terminal app and vscode terminal). If that output is different, maybe that's the issue. If you run pod --version on the vscode terminal, you should be able to see the same error that the vscode extension is getting when trying to validate cocoapods installation.

So when I turned off rosetta mode and updated my gems with gem update the extension doctor could find the pod installation. Maybe just reinstalling the cocoapods gem (gem install cocoapods) instead of updating all the gems is enough.

@asleepace
Copy link
Author

@RuanAzevedo awesome thanks for the suggestion, will try today!

@bewildergeist
Copy link

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.

doctor-cannot-be-dismissed

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

4 participants