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
Is your feature request related to a problem? Please describe.
In our case, we only have the emulator package installed for tests and not for the build job. This causes an error “✖WARNING: The Android SDK is not installed or is not configured properly”. CI builds are often run inside containers, and it may not make sense to have an emulator because nested virtualization may not be supported. So now we are made to install the emulator inside a Docker image even though you don’t need an emulator to build an Android binary.
Describe the solution you'd like
It might be more effective to check for the sdkmanager in order to validate whether the Android SDK has been properly installed. The sdkmanager could have the ability to install the emulator if it is missing and required.
Describe alternatives you've considered
Our solution has been to create a workaround in which there is a file that mimics the emulator in order to avoid the error mentioned above.
Anything else?
I hope to contribute to this issue and am actively looking to solve it if approved.
You can pass the --force flag on CI to skip environment checks, but yes in general improvements to doctor and the checks is something we intend to ship - have a general rewrite in progress on a branch here: #5674
Is your feature request related to a problem? Please describe.
In our case, we only have the emulator package installed for tests and not for the build job. This causes an error “✖WARNING: The Android SDK is not installed or is not configured properly”. CI builds are often run inside containers, and it may not make sense to have an emulator because nested virtualization may not be supported. So now we are made to install the emulator inside a Docker image even though you don’t need an emulator to build an Android binary.
Describe the solution you'd like
It might be more effective to check for the sdkmanager in order to validate whether the Android SDK has been properly installed. The sdkmanager could have the ability to install the emulator if it is missing and required.
Describe alternatives you've considered
Our solution has been to create a workaround in which there is a file that mimics the emulator in order to avoid the error mentioned above.
Anything else?
I hope to contribute to this issue and am actively looking to solve it if approved.
Please accept these terms
The text was updated successfully, but these errors were encountered: