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

React Native Doctor is unable to detect the Android SDK in Windows 10 #2221

Open
bogdanbaghiu opened this issue Dec 20, 2023 · 6 comments
Open

Comments

@bogdanbaghiu
Copy link

bogdanbaghiu commented Dec 20, 2023

Hello I tried to exec the npx react-native doctor and obtain that:
image

I have installed the android-sk 33 and 34, but supported .b33.0.0. I need help please!!

The npx react-native info get that:
image
image

And I installed the latest version (11) from Android SDK Command-line Tools

React native project to test: https://github.com/bogdanbaghiu/test_image_colors

But the check of Android Sdk not pass :(

@szymonrybczak
Copy link
Collaborator

Hey @bogdanbaghiu, that's because you're using expo in your project. So you should use Expo CLI to manage your Expo project, I also see react-native-windows inside your package.json, if you want to use out of tree platforms you should use prebuild, and use React Native Community CLI.

@bogdanbaghiu
Copy link
Author

@szymonrybczak Thanks for your answer! You were right that I had the added library in my package.json and after that I have made several changes to my package.json that I invite you to look at and try. I have made some progress but I will tell you what I have been discovering.

I Delete the node_modules, android folder and package-lock. I did an install npx expo install react-native-image-colors library, I already had it installed but I did it so that the yarn.lock file updates all the dependencies. Then I did an npm install that installed all the dependencies in my project. Next I launched the npx expo run:android command and it created an android build again. It launched successfully on my device. Finally I told myself that I am going to check if the npx react-native doctor command has solved my problem and apparently it still looked the same.

Then I realized that if I delete the android folder from my project I get the following:
image

I have noticed that the npx expo run:android command generates the android build but for some reason it says that the Android SDK supported has to be .b33.0.0 and the ones I have installed are 33.0.0

Could you check if the same thing happens to you with my project but on your computer? If it doesn't happen to you, could you please try to guide me to know why it tells me that it needs an sdk with .b in front of 33.0.0?

@justdan0227
Copy link

justdan0227 commented Feb 1, 2024

I'm having the same issue on Apple Silicon and I am NOT using expo. SDK is there but same doctor results.. Thoughts?

`npx react-native info

WARNING: You should run npx react-native@latest to ensure you're always using the most current version of the CLI. NPX has cached version (0.73.1) != current release (0.73.3)

info Fetching system and libraries information...
System:
OS: macOS 14.3
CPU: (10) arm64 Apple M1 Pro
Memory: 2.34 GB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 19.4.0
path: ~/.nvm/versions/node/v19.4.0/bin/node
Yarn:
version: 1.22.19
path: /opt/homebrew/bin/yarn
npm:
version: 9.2.0
path: ~/.nvm/versions/node/v19.4.0/bin/npm
Watchman:
version: 2023.06.12.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.14.3
path: /Users/km2t7x72tn/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 23.2
- iOS 17.2
- macOS 14.2
- tvOS 17.2
- visionOS 1.0
- watchOS 10.2
Android SDK: Not Found
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9619390
Xcode:
version: 15.2/15C500b
path: /usr/bin/xcodebuild
Languages:
Java:
version: 21.0.1
path: /usr/bin/javac
Ruby:
version: 2.7.6
path: /Users/km2t7x72tn/.rbenv/shims/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.73.1
wanted: 0.73.1
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false

info React Native v0.73.3 is now available (your project is running on v0.73.1).
`

Copy link

github-actions bot commented May 2, 2024

There hasn't been any activity on this issue in the past 3 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days.

@github-actions github-actions bot added the stale label May 2, 2024
@RichyTech01
Copy link

ign)
$ npx react-native info
info Fetching system and libraries information...
System:
OS: Windows 11 10.0.22631
CPU: (8) x64 Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
Memory: 8.00 GB / 15.85 GB
Binaries:
Node:
version: 20.10.0
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 1.22.19
path: ~\AppData\Roaming\npm\yarn.CMD
npm:
version: 10.4.0
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK:
API Levels:
- "31"
- "33"
- "34"
Build Tools:
- 30.0.3
- 31.0.0
- 34.0.0
System Images:
- android-30 | Google Play Intel x86 Atom
- android-34 | Intel x86_64 Atom
- android-34 | Google APIs Intel x86_64 Atom
Android NDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: AI-232.10300.40.2321.11668458
Visual Studio: Not Found
Languages:
Java: javac 20
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.1.0
wanted: 18.1.0
react-native:
installed: 0.74.1
wanted: ^0.74.1
react-native-windows: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: Not found
newArchEnabled: Not found

@github-actions github-actions bot removed the stale label May 3, 2024
@stuttskl
Copy link

Hi @bogdanbaghiu, did you ever figure out why you are seeing the .b in front of the version number? I'm using Expo, and upon running npx react-native doctor I also see that the version supported has a .b prefixed in front of the version number, but I don't know what it's meant to mean.

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

No branches or pull requests

5 participants