After updating to canary preview 5, android studio does not work.
It just show this image and nothing happens
i searched for any solution but to no avail
what is the wrong with it?
Thanks in advance
I have the same problem with my Android Studio version 2 Preview 4 i asked a question here in SO after that i find the solution just look on my answer to my question here
This is what i did
This is an answer for my question, after trying many methods now it works fine.
This is how i resolved my problem by:
Updating Android SDK Tools and the latest SDK Platform
Removing the Android Studio cache folder situated in
C:\Users\<username>\.AndroidStudioPreview2.0
Running android studio again
give it a try and good luck!
Try to reinstall Android Studio. It is not good idea to use Canary Builds because it can be unstable.
I have obsession to have all apps upgraded to the newest version, and I used to use Android Studio Canary builds for a long time, and than some Canary Build caused some problems, and I have to reinstall. From than, I use only stable version of Android Studio.
Related
I recently downloaded the latest version of android Studio and this is giving me a lot of problems. Some of my old projects don't work due to compatibility issues, so I wanted to know if it was possible to revert to an older version of Android Studio and how I can do it
Yes, it is possible.
You can uninstall the current Android Studio and then, you can search here for the version you would like to download.
I have update Android Studio to latest version 3.1.1, but is so slowly , especially when I editing build.gradle file , is there any solution ?
(before I use 3.0.1 , that is so fast)
It seems like this is only happening in China. Try this solution:
https://stackoverflow.com/a/47342580/501175
According to the answer above, there are two ways you can try:
You need to modify the proxy setting of your Android Studio
Simple add a line 127.0.0.1 search.maven.org to the /etc/hosts file. I am using the second one and it works fine.
Well , now Android Studio 3.1.2 has fixed this problem
How's about downgrading Android Studio to 3.0.1? I had the same issue as you. As a result, I downgraded it.
In case anyone wants to download different versions of Android Studio, this is the link you need: Download Archives
It's a reported bug in Android Studio you can follow the issue here
https://issuetracker.google.com/issues/77211316
It's been fixed in version 3.2 canary 11
Edit: They've released this fix with 3.1.2 in stable branch too.
I am using latest version of android studio
and i am open a an older project the android studio not open this project
and always fininshing the gradle while downloading or building it
i have attached the screen shot with this for batter understanding
please help me on this issue these project was build with older android studio like 2.2 and now i am using the latest version which is android 2.3.3 but with this version project was not open properely
android gradle problem the screen shot of the problem
This same thing happened to me, when i was into android. Go to android sdk manager and update whatever it says, and you will good to go.
Even android studio is also trying to do the same thing. but it doesn't show you the progress.
I am trying to get started with Android Things. I am selecting Android Things in Project type in Android Studio 3.0 Canary 2 from May 26 2017.
My gradle build is failing.
What is wrong here? Is this an issue with the Canary build?
I hate to answer my own questions but here I am, hope this helps someone. This issue was the JDK I was using. I was pointing to JDK 1.8 on my computer instead of using the embedded JDK in Android Studio, issue was resolved.
I recently switched to Android Studio from Eclipse and I noticed that the Quick Documentation popup in Android Studio does not syntax highlight the Android documentation. How do I enable this? I have looked everywhere online and still have no solution.I am on Android Studio 0.5.4 on Mac OS Mavericks 10.9.2
Yesterday's update to Android Studio 0.5.5 fixed the problem for me! Seems it must be a glitch affecting version 0.5.4 only!