I've been trying to figure out why my app isn't working, but I can't find Logcat! I just uploaded the new Android Studio release. I've researched and found out where to look to get this message:
ddms: Can't bind to local 8610 for debugger
All the answers I see on SO are for Eclipse. I looked at the developer page, yet for DDMS, it sends you to another page that is full of information for running DDMS in Eclipse!
Please, need some help here! I mean if the dev page is wrong, can't someone show a little love? (Instead of knocking me down 4 points like yesterday. should left in the note I couldn't find my logcat but I was embarrassed.... now not so much .... )
thanks in advance.
I had to open the Android Device Manager to get at the Logcat. It would not scroll through the regular window when the app quit working like it used to (previous to yesterday's and today's updates to Android Studio). As such, I cannot copy and paste code, but can use snagit to capture pngs to post. Thank you. This question is closed.
Check if you have hided it...If it is hiding problems the go through given image to display it or ALT + 6
Related
Design preview console of my android studio stuck at loading. I can't find the solution for that even and reinstalled it.
I had faced the same problem a long time ago.
So what you need to do is go to the View option on the top taskbar. Choose the Tool Windows suboption and inside it remove and add the Preview panel.
View>>Tool Windows>>Preview
This fixed the problem for me. If it does for you as well, do let me know.
I'am a newby in android studio and learning a lot, but now have a problem where i cannot seem to find the answer to.
In android studio you can visualy drag&drop your screen.
I have seen it can do al lot (although you sometimes need the xml) but for me it is not working at all.
I mean i cannot drag&drop any widgets on the screen at all.
Tried changing the theme: no help (really tried a lot of them)
Tried a complete new project: same story
Tried other APK verion: same story
Tried Invalidatd caches / restart: no help
Even with a new project (EmptyActivity) it add's a android.support.v4.widget.NestedScrollView and then gives error's on that
(Failed to find style 'coordinatorLayoutStyle' in current theme).
It also gives an error on layout_height/layout_with not being there. But they are there for each widget.
Please do not missunderstand: when i execute the project i runs just fine (both on phone and emulator) but the visual builder for the screen.....:-(
Does somebody knows how to solve this.
If more info is needed please ask.
Any help is more than welcome.
There are several things that could be causing this:
Your caches could be messed up. Try going to
File > Invalidate Caches / Restart ... (I know that you already tried this, but posting for future views.)
Also, make sure that you don't have Drag-n-Drop with ALT pressed only checked in your Settings (Appearance & Behavior - Appearance).
Finally, in a default project created in Android Studio, there are two XML files created for each layout. For example, content_main.xml is embedded within activity_main.xml. Make sure that you are using content_main.xml for your design work.
In the end i fixed it by changing the SDK version in de gradle file.
still do not understand why it was wrong as studio genereded it that way but now it works so.... for me: case closed.
When I build a project and there are errors, the Messages window that shows all the errors does not always show. I have to build the project (i.e. Ctrl + F9 ) twice or more in order to see the window.
When the window is not shown, View > Tool > Messages Alt + 0 is grayed out as shown by the following screenshot. How can I show the window when there are build errors?
I am running the latest Android Studio on Windows 8.
[Edit] 2018-04-02
Android Studio 3.1 seems to have this window removed, many people may come here because of missing the Messages Window due to a different reason, and yuval's answer may be the right one in this case.
I got here after upgrading to Android Studio 3.1, in which they removed the Messages window, replacing it with the Build window. After some poking around, I found this button on the left side of the Build window:
Clicking this button toggles the view between the new "Build" view and the old "Messages" view.
UPDATE: per suggestions in the comments, since this doesn't really answer the asked question, I opened it up as its own question: Where is the Messages Window in Android Studio 3.1
UPDATE 2: In Android Studio 3.3 the button now looks like this:
UPDATE 3: In Android Studio 3.6 the button is gone. Instead, the build window is permanently split between text output and visual output. If you can't find the text output, it might be fully collapsed, so look on the top right of the build window for something like this:
And try to drag it left to reveal the build window, like this:
It was a bit different in my case. I just closed the Message Tool Window with this red cross on the left and then this window completely disappeared and would not show again even after several rebuilds, View > Tool > Messages Alt+0 was also grayed out. The only thing that helped to bring the Window back is to break the build, so it would be some compiler errors. After that the window has reappeared showing those errors. Now the window is still there, does not vanish. Hope this helps somebody.
Just to have the whole picture. Go to the Build and then on the left side of the window you will find your Messages icon.
Build -> Make Project
(Ctrl+F9 or ⇧⌘F9)
Can't find the button #yuval provided, but here it is to toggle to show it
I am wondering if anyone else has had this issue with visual studio (or a VS extension because I have a few installed) and what is causing this? The number goes away when I close visual studio and I have not been able to figure our what is causing this. The number is overlayed on my desktop and not just visual studio. It covers all other windows I have open as well telling me it's set to be always on top.
Anyone else come across this issue or what is causing it?
I figured it out!
This has been bothering me for years. I finally just sat down and solved the problem. Basically, VS has this little known feature where you can navigate through code lens with just your keyboard. If you press Alt for a couple of seconds, you will see numbers just like the ones that appear at the top of your screen above your current method. To fix it, just long press Alt again and the number should go away. If you have many VS instances open you might have to go through them one by one.
I don't have significant reputation to comment, but I am experiencing this both with VS2013 and VS2015 too. The only extension I have installed is Resharper.
My research shows that it is caused by the hover text / overlays from various components. The only way I have found to get rid of them is to close the Visual Studio IDE window responsible.
I've had this issue several times and usually I can just shut down the program and restart it. But this time I have a bunch of windows open and I don't want to restart Dreamweaver.
My problem is that Dreamweaver brought up a code hint, but the code hint box now won't go away. It just sits there floating in the middle of the page. It doesn't matter if I click to Preview or any other tab in Dreamweaver, it still just sits on top of everything.
I'm working on a Mac, Dreamweaver CC (cloud, fully updated). Anyone else have this problem???
This has been a HUGE PAIN for me as well! You can make the code hint disappear though by finishing out an element that is in the code hint box. For instance if the code hint box appears and you can see class in the drop down... create a <div class="xyz"> real quick and the code hit box will dissipate after you close the quotes on the class because you used an element in that box. As to why this continually happens on the Mac version I have no idea, but I hope they fix it soon!
It's a known bug since years as you can read here: https://forums.adobe.com/message/7745689
Someone suggests as a workaround to set the Coding Hint delay to 0 (as said here: https://forums.adobe.com/message/7745689#7745689) but for me, in Dreamweaver CC 2015 Windows fully updated via cloud app, this bug still occurs while I code JS files.
Awaiting for a final fix, I hope this suggestion can be useful for you on Mac. :)