I know how to fix the problem, but the thing is, my .android directory became invisible, and i don’t know how to delete it. I tried with command lines like : rmdir /S .android, and it didn’t work. I’m on a mac.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I know how to fix the problem, but the thing is, my .android directory became invisible, and i don’t know how to delete it. I tried with command lines like : rmdir /S .android, and it didn’t work. I’m on a mac.
It’s okay i found it :
On the OSX platform, if you manually remove the ~/.android directory using rm -rf ~/.android, then try to run the emulator, it crashes. This happens because the emulator fails to create a new .android directory before attempting to create the child SDK1.0 directory. To work around this issue, manually create a new .android directory using mkdir ~/.android, then run the emulator. The emulator creates the SDK1.0 directory and starts normally.
And i had to recreate some AVD, that’s all.