You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[✓] Skip version 0.10.1 (= 0.10.1)
[✓] macOS version 14.5 (> 13.5.0)
[✓] macOS architecture: ARM
[✓] Swift version 5.10 (> 5.9.0)
[✓] Xcode version 15.4 (> 15.0.0)
[✓] Xcode tools SDKs: 5
[✓] Homebrew version 4.3.9 (> 4.1.0)
[✓] Gradle version 8.9 (> 8.6.0)
[✓] Java version 22.0.1 (> 21.0.0)
[✓] Android Debug Bridge version 1.0.41 (> 1.0.40)
[✓] Android Studio version: 2024.1 [!] Android SDK licenses need to be accepted with: ~/Library/Android/sdk/tools/bin/sdkmanager --licenses
...
Android Studio comes with command line tools packaged (not need to install separately) at the location: ~/Library/Android/sdk/cmdline-tools/latest/
old location/command line tools package is not longer supported: see https://developer.android.com/tools/releases/sdk-tools
Even symlinking old tools package location to new commandline tools, and accepting licenses with new command line toold sdkmanager will not help to avoid this issue.
The text was updated successfully, but these errors were encountered:
[✓] Skip version 0.10.1 (= 0.10.1)
[✓] macOS version 14.5 (> 13.5.0)
[✓] macOS architecture: ARM
[✓] Swift version 5.10 (> 5.9.0)
[✓] Xcode version 15.4 (> 15.0.0)
[✓] Xcode tools SDKs: 5
[✓] Homebrew version 4.3.9 (> 4.1.0)
[✓] Gradle version 8.9 (> 8.6.0)
[✓] Java version 22.0.1 (> 21.0.0)
[✓] Android Debug Bridge version 1.0.41 (> 1.0.40)
[✓] Android Studio version: 2024.1
[!] Android SDK licenses need to be accepted with: ~/Library/Android/sdk/tools/bin/sdkmanager --licenses
...
Android Studio comes with command line tools packaged (not need to install separately) at the location:
~/Library/Android/sdk/cmdline-tools/latest/
old location/command line tools package is not longer supported: see
https://developer.android.com/tools/releases/sdk-tools
Even symlinking old tools package location to new commandline tools, and accepting licenses with new command line toold sdkmanager will not help to avoid this issue.
The text was updated successfully, but these errors were encountered: