My studio's current version is 0.9.9 (recently updated), now here is the history:
There was some problems when I shifted eclipse to studio. The last problem happened when I updated it. My app became full of error. One of them was cannot resolve Symbol ActionbarActivity. And so many others. I spend a day behind it and gave up. I recreated my app from first to last with the same resources, then it became totally good to go. Three days later(today) again another problem raised. I turned on my laptop, opened Android studio and it says Rendering problem No Android SDK found. Please configure an Android SDK. But last night it was running fine. Now there is no design window.
I am wondering that why the errors come automatically. I don't do anythings in the settings stuff of the studio. I just develop my app. I just write code and make my app. So whats wrong with the studio. It crashes without any reason and I have to waste the half of the time. Is this a kind of jokes? It too much irritating. Updating latest version is not the reason. The problem is occurring from whenever I downloaded the Android Studio and shifted from Eclipse to it. With 2 or 3 days intervals it comes with new problem.
I suggest you to try fresh Installation or, As it happens because of some internal Intellij's libraries problem.
Related
Hey guys and girls for a the past week I've grown a lot of interest in android studio (even without knowing quite much about it) I decided to create an app that I deemed quite useful. However the app required maps to be integrated in it and I really did not know what I was doing and at one point I started messing with the settings and then all hell broke loose and I kept getting AAPT2 errors and I even tried to fix this issue with the gradle properties line that you add (I forgot the line of code to add). Anyways it still didnt work. However I rembered that I always kept the good version (before I broke everything) of the app on my phone. So when I go in my phone the app is there and it works just fine. Ive tried so many things to get the source code from the app on my phone without any succes. My question is, how can I get the source code back from the working app onto my laptop to continue coding in android studio? If it helps I am using Linux 18.04 LTS and running the newest version of android studio. Thank you for any help from you guys. This means a lot to me.
You can’t get back the ‘source code’ from an already compiled app.
You should consider using some version control platforms like git from the next time
I am facing a weird experience with Android studio that during when it suddenly hangs, the previous changes that I made in my project are not saved. This issue happened for me several times when I close the Android studio manually from Task Manager during system crash or when I get Android studio not responding error. This kinda error is not occuring if I save the workspace often through ctrl+s(Save) or ctrl+shift+s (Save All), but these issues I have never faced with Eclipse previously I used for development. So kindly please mentor me whether is there any settings that I have to change or update in my Android studio to resolve this issue. Your solution would help and useful for me to prevent my code from losing the changes I made. Thanks in advance.
Please text me if my question is not clear. Expecting your valuable answers and solutions. I have been facing this issue since I started using Android studio and because of this I have lost lots of data in my code.
Have you allocated the correct amount of ram to the avd? As well as having enough to run studio anyway? Additionally Cpu can be an issue if you're using something like an i3 or low end i5.
I can't run studio on my laptop due to it being generally bad but also the Cpu can't take the load.
Came over a very strange problem with Eclipse.
I'm using Android platforms 4.0 to 4.4. And when i'm for example switching the tabs or opening a new tab in the top that shows the current opened layouts/views Eclipse starts to load all platforms again (Loading data For Android 4.x), from 4.0 to 4.4, and then rebuilds the workspace.
This makes Eclipse totally unusable as it's crashes when switching views. I hadn't this problem a couple of days ago, it started acting up after I received a update from Eclipse for two/three days ago.
Anyone knows what the problem is? Or can help me solving it?
I experienced the same issue, and the solution was to download the SDK again from Android: https://developer.android.com/sdk/index.html
I tried to revert the ADT from 22.6.0, which was the one giving this errors, to 22.3.0, but couldn't do it manually. So the solution was to download the SDK again from Android, because ironically, the online version at the time of this answer is still the old version of ADT (22.3.0), which works.
Hope it helps!
I'm trying to start out with Android programming (I'm running Mac OS X Lion). I had an old version of Eclipse and installed ADT version 20 in it, and code didn't compile properly. Fine; I hadn't done much in there, and after reading some stuff here it sounded like the easiest thing for the long run would be to put together a completely new installation.
So I downloaded the latest version of Android, with the SDK, from the Android developer Getting Started site, and ran it (in its own directory). I loaded one of my previous workspaces and it said that one wouldn't work because the ADT was version 20 and it needs 21. I figured fine, there wasn't much in there and I'd just start a new workspace.
So I started a new workspace, and here's where the real trouble came: It gives me the start screen with newbie welcome instructions but won't go any further than that. When I try to create a new Android Application Project, it goes through the menus but as soon as I click Finish I get a please-wait circular icon, and little happens. There's a line at the bottom that says "66M of 142M" - it increases slowly into the 80s and then drops back down into the 60s, endlessly. And the links provided on the welcome page (Building Your First App, etc.) don't work - I click on them and nothing happens.
Any idea what's going wrong here? Is there some cruft left over in my system from older versions, which I should delete? If so, how should I go about doing that? If not, what else might I try to get it working?
I can't comment beneath yours because of my level, but you can help Eclipse run faster by giving it more memory. Doing this speeds things up quite a bit.
As far as installations go, maybe try Google's packaged version of Eclipse + Android SDK. The whole package is available here. It's already preconfigured to work and provides eclipse with ADT installed by default. Of course, if you already have an existing Eclipse you want to modify this won't help you too much. But if you're new to Eclipse it's a good way to get started with Android development.
Like the question says, no mater what project i try this on, old or brand new, when I right click on the project and go to properties, then select the Android tab (I want to add a library), Eclipse freezes. I have to kill it. Has anyone run into this problem or know how I might fix it?
Thanks
EDIT:
Eclipse SDK
Version: 3.6.2
Build id: M20110210-1200
EDIT:
Or is there another way to add a library. I want to try out ActionbarSherlock :)
Ok, so I don't claim to understand it, but I've tried it more than once and confirmed it. When I'd go to the Android tab in Properties, the window automatically stretches the full height of my monitor and freezes. So, I killed it and went back in, but this time, starting on a different category ("Resource" in this case), I squashed the window height down to almost as small as it could get and clicked on Android. It worked. Didn't freeze. Then I was able to expand the window to see the list of libraries. No idea what it is, but I did it several times...recreating the freeze and then the fix. Hopefully this will save someone else...
i have found the reason ,because the list of available Android sdk is too long ,the window of the property can't be drawn immediately ,so it has no response.
the solution is open the SDK Manager ,delete the old sdk platform ,such as 1.5 1.6 3.0 3.1 3.2
those are not used usualy.then restart the eclipse .it works now .
For these kind of problems you have to try the following (in the same order) and stop when it works.
Play around inside eclipse by closing and opening project, deleting and reimporting projects etc.,
Restart eclipse
Restart system
Upgrade to the latest android SDK
Upgrade to the latest eclipse version
Usually you should stop at 2. Sometimes you need to stop at 3. Occasionally at 4 and Rarely at 5.
Good luck.