-
-
Notifications
You must be signed in to change notification settings - Fork 297
installing Android Mode on a machine that's never run it throws SDK errors #151
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
Comments
which OS ? |
OS X and Windows. |
Hi, I am also having the same issue in OS X |
I can reproduce this issue (on OS X). After closing the "bad day" warning, and then switching to the Android mode in the PDE, the SDK selection window does show up, where one can choose between "Locate SDK path manually" and "Download SDK automatically". However, clicking on "Download SDK automatically" does not trigger the SDK download. This functionality used to work in a recent beta (probably 6). @omerjerk do you have time to look into this? |
I manage to direct my processing towards the Android SDK File, by selecting the "Locate SDK path manually", as initially I could not view the Library directory to show. It does not prompt me the above erros as "bad day". Yes! the "Download SDK automatically" does not trigger, although it shows that it completes the download. However, after all is complete, now processing shows an error of that "could not create a virtual device for the emulator". |
Fixed with a807917 |
Complains that the Android SDK is not available and that the Mode will be all but disabled, but doesn't prompt user to do SDK installation.
The text was updated successfully, but these errors were encountered: