I am using the Android emulator that came with the Android Studio SDK. I have several set up and they all do the same thing.
I am on MacOS Catalina latest version.
The first time I did a screenshot today it worked fine. It saved the shot on my desktop.
I then went to take a second shot and in the emulator it shows it took it, but no file showed up in Desktop.
I took several more and they just don't show up. I used Finder to search for the name that is showing in the emulator tool and they are not found anywhere on my hard drive.
I can delete them, take more shots and they show up with a preview in the emulator tool, but I can't find them anywhere on my hard drive.
Any ideas?
When I try to inspect my application's layout in a simulator, by going Tools => Layout Inspector, it always fails with one of the errors:
1.
Error obtaining view hierarchy: There was a timeout error capturing the layout data from the device.
The device may be too slow, the captured view may be too complex, or the view may contain animations.
Please retry with a simplified view and ensure the device is responsive.
2.
No active windows displayed by com.instabridge.android.dev
The layout is not particularly complex, and it does not contain animations, just map with some views. Android Studio is 3.4.1. How do I fix it? Or how to find the cause of the errors?
Found a really strange solution.
Open your app, go to android home screen, open another app, now use Layout inspector in Android Studio.
It worked and I see my app's view hierarchy.
UPDATE
P.Melch claims that you don't even need to open another app, try just sending your app to background.
I had the same issue on Android Studio 3.4, but I was able to use the Layout Inspector on Android Studio 3.5 Beta 1 without any problems.
I am working with a very complex view, so I suspect that is what led to the trouble on Android Studio 3.4. Both the failure I saw and the success were with a physical device.
Try to use a real device instead of the simulator.
When running the simulator and android studio, your laptop/mac/whatever might be running out of memory.
I always prefer to run the layout inspector on a real physical device. It works the same as with the emulator once you're connected with adb
I cannot run any virtual device on Android studio. Every time I get black screen and error as shown on the picture: screen
.
Week ago everything worked properly.
You can create emulator without device frame. Like this
Hey, this is an example of the issue I'm having with Android Studio. I dont think I have made any changes from my first few programs which worked fine and the UI filled the whole Emulator screen
This is the 4th ever app I've written for a web dev class with android studio. I have written 3 other apps that did not have this issue with the phone. But after starting up android studio today to work on the next project for a class the issue in the picture would take place. The Virtual phone works properly but just has a very badly sized image instead of the full virtual phone screen.
I've sent a copy of the program I've been working on to my professor, but haven't heard back yet. Ive also tried to uninstall and reinstall Android Studio but the issue still remains. If anyone can give me a few hints or help in resizing the image to the correct size in the Emulator it would be much appreciated. Thank you very much.
The story is that I developed an Android program with Android 4.4.2. But some problems was found after installing the program to a device with Android 5.1.1. So I tried to download Android 5.1.1 for my SDK to debug the problem. Then the AVD I kept on using becomes like a mess no matter I changed to different configuration (see picture 1). My AVD configuration is as picture 2.
Hope someone could help... Thank you so much!
Picture 1
Picture 2
Got a temporary way to solve it and don't know if it is correct.
Set the skin to "no skin".
There is another problem happened now. The control bar of that window shows out of the screen. It makes the window cannot be moved. Anyway, I can continue my development job in this way...