This happens every time I run a test as long as I remember (Android Studio 2+, 3.0, 3.1, 3.2)
.
Sometimes the stop button even shows multiple processes. Also it doesn't matter how many times I click the stop button, it will never work (it does stop the test but the button remains in active state).
It seems to be a bug in Android Studio. I have found that it was reported previously on Google Issue Tracker with ID 64031765 and is not fixed yet.
For some reason my answer was deleted by a moderator without any explanation. It is a bug and there is nothing more to add.
Related
I encounter a problem where my Xamarin Forms Android app won't start (blank screen) after I change the Android OS date to an earlier date. I only happens when it's not connected through the debugger.
I'm using the latest version of Visual Studio and Xamarin. At the time of this post, I tested with:
Visual Studio 2019 - 16.6.2 (Also happens in 16.5.3)
Xamarin Forms 4.7.0.968 (Also happens in previous 4.X versions)
Phone: Samsung Galaxy S8, Android 9.
Steps to reproduce:
Create the sample Xamarin Forms app using the "Blank Page" template.
Run it through the debugger first (The app works and displays the welcome message).
Close the app.
Set the OS date/time to manual and go back one day.
From the phone itself (without using the debugger), run the app.
After the last step, the app won't start but will instead display a blank screen. No crash. Resetting the time to automatic date when the app is closed, the app will run correctly again. If I do the same procedure but always start the app using the debugger, everything works fine.
Does anybody knows how to resolve this issue?
Edit: Since it doesn't happen while the debugger is attached, I added logs so I can use logcat to know where it reaches. When it hangs, it doesn't even seem to reach the "Oncreate" of my MainActivity class.
I tried your steps and reproduced the issue , it shows white screen on my side and it seems be stuck .
The problem only occurs when i set time to earlier date , it works fine if i set it later date.
I have raised the issue on github : https://github.com/xamarin/Xamarin.Forms/issues/11128 , you could monitor the progress.
I have an Android app with a corresponding Widget. It works perfectly in the past before 2017Nov. However, After my update to the Android studio, Gradle, and build tools. The app always build with an app that cause "Problem loading widget"
.
To make sure I am right I get back my code version before 2017Nov, and recompile. Problem still here. To solve this problem, my only way is to reboot the device. After reboot the device, the widget loads normally. My question:
What kind of special system calls the Android device will trigger when restart the device?
More information: Actually I have done one more test. While my widget is live and no problem is shown after reboot, I uninstall it, reinstall it. Then problem loading widget immediately appear. After that reboot, problem gone.
My app freezes for some time while the first opening of the app. From there on app fires up with no time. Why is this happening and any ways to fix this? I have tried adding a Simple Activity with one small image, even then it freezes for the first time.
There is a strange issue with newly released Android Studio 2.0 or 2.1. First time of launching application take longer than usual. This issue happens only in debug mode and not effect to your released APK. Also I was suffering this issue and found this solution.
Settings/Preferences→ Build, Execution, Deployment → Instant Run and uncheck Instant Run
Have submitted the following bug report for Google. May be somebody faced similar problem?
Android studio 2.1.2 for Windows may suddenly stop responding on keyboard or mouse clicks.
Also, when trying clicking windows close button (cross), nothing happens.
Task manager shows, that AS consumes about 30% of CPU. The only way to stop AS is to kill it via task manager.
Just before freezing the following message occurs in AS status bar:
null java.nio.BufferOverflowException at com.android.ddmlib.Debugger.read(Debugger.java:210) at com.android.ddmlib.MonitorThread.processDebuggerData(MonitorThread.java:451) at com.android.ddmlib.MonitorThread.processDebuggerActivity(MonitorThread.java:394) at com.android.ddmlib.MonitorThread.run(MonitorThread.java:259)
This may occurs in any time, even when just editing text.
I keep getting the message 'Activity not started, its current task has been brought to the front' despite making changes to the code. I wasn't aware of changing any settings in Eclipse besides creating a new AVD and it was working fine earlier today. Now it's not reinstalling at all.
I'm not sure why the problem started when it did but I installed some updates from Eclipse and Android and it seems to be working fine now.
There are several thing that you can do to solve this problem:
You can close your AVD and then start it again.
You can manually uninstall your application using AVD interface (Home - Menu button - Manage apps - All tab - Your app - Force stop/Uninstall).
The solution was to start the task manager and end multiple AVD emulator processes that had somehow built up.
i also constantly have this problem, even when i change the code. what helps for me is simply to start my application in the debug mode; then it starts without that warning. later when i start the application in the non-debugging mode again it normally starts without that warning (at least for a while).