I updated the android sdk today - since then I have had the following problems
stopped exporting apk ( but doesn't tell me why)
can't run emulator (message on console says it cannot find *.apk)
I tried reloading project, after getting message that id did not exist (even though it was there)
managed to get eclipse to recognise project, but now it rejects the switch/case statement on my options menu
All this worked yesterday - and I have looked at most of the solutions put forward on other posts - and none seem to work.
currently I am on android sdk tools 23.05 and eclipse Luna 4.4.1 (running on Linux as that may be a factor)
Has anyone any idea how to solve this - any suggestions greatly appreciated.
I managed to get things to work, although I was now getting an error related to case statements in libraries. I checked the properties, and the project was not set as a library so I couldn't understand this.
I then tried the one thing I should have done first - what I would have done thirty years ago when first in IT - I completely rebooted the whole system.
Now eclipse showed the project as being a library, so I was able to reset that and everything now seems to work.
I can only assume the update yesterday messed up some of the memory, and the eclipse lost its bearings.
Related
Background
I'm trying to use Android Studio 3.3 Canary 8 (the latest Preview release). I'm running Ubuntu 18.04 LTS 64-bit, and if it's relevant, my desktop environment is KDE Plasma and my window manager is KWin.
Issue
It was working completely fine until a couple of days ago, when I began experiencing an unusual display bug which rendered the editor completely unusable for me.
Here are a couple of screenshots of what Studio looks like right now. The first one is the Tip of the Day window that pops up at startup, and the second one is the actual editor itself.
From what I can tell, it seems that all UI elements have been stretched vertically, or something along those lines.
Troubleshooting
I tried Googling around for my issue, but I'm not entirely sure what to even Google in the first place. I tried some variations of "Android Studio display bug" or "Android Studio UI vertically stretched", things along those lines, but most search results apply to Android applications and not the editor itself.
I suspect that there's an issue with Android Studio's DPI detection, but I have no way of fixing any issues there given the fact that I can't see any text anywhere.
Attempted Fixes
I tried redownloading Android Studio from their website and running that fresh install. No dice.
I tried completely removing any Android Studio configuration or cache folders and reinstalling. Nope.
I tried using the release candidate instead of the Canary build. That didn't work so I tried using the stable release (3.1.4), which didn't work either.
I tried rebooting my computer too, but the issue persists.
I can't think of anything on my computer that might have changed between the last time Android Studio worked fine and now. I do remember installing some system updates, but I'm not sure which ones specifically (if there's a way to find out what updates were installed for a given run of sudo apt upgrade, I can include that information in this post).
Bottom Line
I'm really at a loss, and this is a really frustrating issue. Any help would be greatly appreciated, and if this is the wrong place to ask I apologize. If there's any more information you might need to troubleshoot this, please let me know and I'll update this question.
I'm on Windows. I created a new project on Android Studio for Marshmallow at least.
The only thing I've done so far is generating the main activity which is a tabbed activity with view pager. Also, you should know that this project is a private git repo that I cloned.
I'm working on this project with another developer and the project is perfectly working on his side.
The problem is:
When I try to launch the app (wether it is a virtual device or my real phone), the gradle build gets stuck at the app:processDebugResources step. I waited more than an hour and nothing happened. Moreover, when I want to cancel the gradle build, it doesn't respond and I have to kill Android Studio process. Then I restart Android Studio and I have to kill a gradle process that prevents the initial gradle build (at Android Studio startup) from working.
The crazy thing is that I was able to launch the app before. I even installed it on my phone!
What I've tried so far:
Do what stackoverflow was giving as solutions like tick the offline mode in the settings
Create a new project --> It doesn't change anything
Reinstall Android Studio --> It doesn't change anything
Deactivating Avast antivirus
Invalidate cache/restart + Clean + rebuild (the rebuild gets stuck like when I try to launch the app)
And maybe other solutions that I forgot...
It's getting very annoying as it's making me lose days of development.
If you have any more solutions, or if you think I should try again some of the previous solutions, help would be greatly appreciated !
I know this is an old post, but I faced the same problem during the last few days and since i got crazy I hope I can help someone else out there.
After many hours of troubleshooting I found that the Java Platform SE binary executable goes in "suspended mode" in Windows 10, preventing Android Studio from compiling (it hangs at app:processDebugResources).
Example Screenshot
Killing the suspended process and recompiling the project works just fine... until Java gets suspended again.
Maybe your gradle version is not compatible with it. Try again with latest version of gradle in your project.
I did several things:
Install NDK
Change JDK from embedded one to Jdk 8
Redownload SDK i was using (6,7,8)
And now the problem is solved ! I have no idea which of these things made the tricks but I'm happy ! It may be useful to someone else one day.
I had no problems installing the "android bundle kit" (eclipse + ADT) on Slackware64 14.0.
However, a lot of weird errors appeared with the project, and when trying to run after a lot of suffering, I receive a "Segmentation fault".
I thought that was an installation failure on my "multilib" and I reinstalled it, again.
"Segmentation fault" persisted when trying to run adb.
So, I remembered I have a functional skype installed in my linux.
Then, I changed all files on "/usr/lib" using the ones on skype directory.
Believe or not, now my android tools are working (fine!)
This is not a great solution, but I was desperate and this saved me.
What is the proper solution to this problem?
Then, I changed all files on "/usr/lib" using the ones on skype directory.
A segfault is just a crash. You should have looked at the stacktrace to figure out exactly what library was at fault and tried updating that library (or searching the internet for help) rather than clobbering everything with your "skykpe libraries"
Given your approach, I suspect you have done more damage to your system than you realize.
These are the errors that i am getting when i attempt to run my project. It was working perfectly fine till yesterday. I have no idea what is causing the error. I cleaned the project and reran a number of times. I even restarted my laptop, but in vain. Please help me restore this, its a very huge project.
My friends copied the project on his laptop and was able to run it successfully. Which concludes that there has been a problem with my eclipse.
There are too many errors to sort out. I would very much recommend the easy way out which is to uninstall Eclipse (in case it really is the source of the problem) re-install it and start up a new project, then slowly add in the project files one by one. At least this way if the error comes back you know which file it is (if any). Best of luck.
Try to update eclipse if there is any update to apply.
I recently completed my first, very basic Android application however when debugging and testing I encountered what seems to be a very common problem. Eclipse and the emulator were giving me a similar problem to this emulator.exe has stop working?, and then after trying the recommended solutions I started receiving errors similar to this Android Emulator won't run application started from eclipse and receiving errors in Eclipse saying this:
adb is running normally.
Performing 'activity' activity launch
Automatic Target Mode: Preferred AVD 'TestAVD' is not available. Launching new emulator.
Launching a new emulator with Virtual Device 'TestAVD'
emulator: warning: opening audio input failed
None of the solutions I found worked unfortunately. Worked as in I was able to run my application in an emulator at all. So I decided to uninstall and reinstall the Android SDK. I followed the instructions in both a Beginning Android Programming book and the ones provided on the official Android website but to no avail. From the last time I downloaded the SDK, the Android SDK Manager is newly updated although appears to install correctly with no new errors. Also reinstalling the ADT in Eclipse seems to go smoothly. However I've noticed that when I now go to recreate a new Android project, it creates it differently to what the website and my book describes. The most prominent difference being that in my drawable folder, there is only an "ic_launcher.png" as opposed to having three folders for ldpi, mdpi abd hdpi. The AndroidManifest.xml also does not recognise android:targetSdkVersion or android:installLocation anymore saying there is no resource identified found. Another major problem is in my MultiTouchHandler class, MotionEvent variables such as ACTION_MASK or ACTION_POINT_ID_SHIFT for example, have the error cannot be resolved or is not a field. Before I uninstalled everything, these things worked perfectly and the application encountered no errors. The app worked!! Upon reinstalling everything, and moving my application into a new project to fix the initial problem, nothing works anymore.
I have googled and searched these forums for a good few days and all the solutions that have been suggested have not worked for me. I have uninstalled and reinstalled and redownloaded the SDK's I don't know how many times and I really don't want to give up on developing for the Android.. but I just can't seem to find a solution. Sorry for the lengthy post but I wanted to be thorough! Any help would be very much appreciated! Thank you!