When I click debug in visual studio on an Azure project I keep getting the same following error every time:
In the background, the other parts do run and the emulator runs but none of the logging functions work. I am running a pretty clean Windows 8 install (downloaded from DreamSpark) with a clean Visual Studio 2012 Ultimate RC installed.
How can I fix whatever is going wrong?
I had the same problem and discovered that this seem to work
If I reboot and then start the azure emulator from the azure command prompt. Works fine.
If I then shut down and exit the taskbar icon and restart from the command prompt, I get the error again.
Checking the running processes, it seems that dfmonitor.exe does not terminate and continues running.
If I terminate dfmonitor.exe and then restart the emulator from the command prompt, it starts up fine without the error.
It started working suddenly without any changes made.
Related
Since upgrading to AS 3.4 I can no longer debug any of my apps. I have made no changes to any of the projects, I just upgraded AS. Now all I get is "Waiting for application to come online".
When I click on Run->Attach Debugger To Android Process, there are no processes to attach.
The apps load and run, but I cannot debug them.
Is there anything I can do to get the debugger working?
(I have tried clean, rebuild, invalidate cache and restart, make project and gradlew clean).
I found the same trobles in Android Studio Dolphin (2021.3.1) when created a new project with no activity. After the project creation I created a main activity and add a launcher intent-filter and tried to debug it. And found "Waiting for application to come online". I found that "Launch" argument in "Lunch Option" for my "Run Configuration" is "Nothing". Problem solved by changing it to "Default Activity"
To change run configuration option select Run->Edit Configurations, or "Modify Run Configuration" in Run or Debug panel.
I had the same problem, I tried: Update Android studio to 3.5, restart cache, delete cache folders, killing adb server and restart it... but nothing works.
I solved executing the next commands on ADB terminal:
On windows, you have to change to platform-tools folder path in order to excecute ADB commands, something like this:
cd C:\Users\YourUser\AppData\Local\Android\Sdk\platform-tools
Then, compile your app on debug mode. (I think shift + F9 on Windows), when you started to see "Waiting for application to come online" message, execute the next adb command:
adb shell am start -n com.example.yourPackage/com.example.yourPackage.MainActivity -D
Just change com.example.yourPackage and make sure MainActivity its your Luncher Activity inside your Manifest File.
I get an error while trying to run any app on a physical device.
Device emulator-5554disconnected, monitoring stopped.
Error while Installing APK
It works after trying at least 3 times, but sometimes it gets frustrating.
I tried to delete all the emulators and reinstall Android Studio but it didn't help. and the set deployment target is always flashing like so:
flashing emulator error
In my case it looks like Docker interferes with adb.
I tried restarting Android Studio, adb kill-server && adb start-server, and anything else I could think of.
Then I tried killing all docker containers and quitting the docker app, and everything works nicely again! Edit: Killing the containers is enough
I'm wondering if this is a newly introduced issue in Android Studio/adb/Docker - I updated to AS 3.4 recently, and I don't remember having this problem in the past, but it could have just been a coincidence.
I tried the suggestion but it didn't work, after a few days of work on it, I found out that a vpn software (SoftEther) that I had installed was causing the problem, uninstalling it solved everything.
it seems adb was interfering with a network bridge the software was trying to create.
Try restarting the adb.
Use the following command to restart adb
adb -d kill-server && adb -d start-server
Use command -d for real device and command -e for emulator in case both are connected
Also if that doesnot work clean the project and reset connected emulator.
Run Emulator and wait for the home screen of the Emulator to load
Click Window > Open Perspective > DDMS
In Devices Panel, click on drop down menu > Reset adb
Run project
When I run my application I get an alert:
ADB not responding. If you'd like to retry, then please manually kill "adb.exe" and click 'Restart'"
By which application is not running on devices, no adb.exe is running in task manager. I found several solutions but they didn't help me.
ABD is not responding often occurred while using Android Studio 1.5.1. Hope it will be fixed in next update
Now, You need to reinstall your Android Studio before that restart the system if it worked no prob otherwise do it on Studio.
Lately, I encounter a lot of problems using Android Studio.
I'm using Android Studio 1.5.1, with gradle plugin 1.5.0 (corresponding to Gradle 2.2.1, I think), on Windows 7.
There is no update for Android Studio for now, and neither in standalone SDK manager.
Sometimes when I try to launch my app on an emulator, the builing process wont stop (I waited for 1 hour once...). Even after I quit the emulator and just build project on sync gradle, it launch a process that never ends. The log file is not writing and there is no error message anywhere.
For the process to end, I have to go to the taskmanager and stop every java.exe process I see, and it then shows this message :
Error:Unable to start the daemon process. This problem might be caused
by incorrect configuration of the daemon. For example, an unrecognized
jvm option is used. Please refer to the user guide chapter on the
daemon at https://docs.gradle.org/2.8/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
After that, not any build will succeed, and the only way for my project to successfuly build is to reboot my OS ! (even after taskkilling every known related task, like android64.exe, adb.exe, java.exe)
Is the bug known ? Is there any workaround ? Am I doing something wrong ?
Further details
When it bugs, the gradle console is writing
Executing tasks: [:app:generateDebugSources, :app:generateDebugAndroidTestSources, :app:compileDebugSources, :app:compileDebugAndroidTestSources]`.
, but then nothing. It's more that gradle is not working than it's stroking on one point. But there still is that java.exe process with its 66Mb of memory...
It bugs after approximately 8 successful runs.
Last updates
I know now the real troublemaker ! It is C:\Users\Me\.gradle\daemon\2.8\registry.bin
I can't even right click on it without crashing Windows Explorer !
I have been facing the same problem. However, I had a previous project which had been successfully built. What I did was - changed the location of Service Directory Path(the one pointing to the '.gradle' folder) of my new app to the Service Directory Path of the successfully built app, i.e from
C:/Users/YOUR USERNAME/AndroidStudioProjects/CURRENT APP/.gradle
to
C:/Users/YOUR USERNAME/AndroidStudioProjects/SUCCESSFULLY BUILT APP/.gradle
To change the service directory path-
go to settings --> Build, Execution, Deployment --> Build Tools --> Gradle --> service directory path
I have a very odd situation here:
I just want to run and debug my app on the emulator.
I get
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.example.myapp"
pkg: /data/local/tmp/com.example.myapp
Success
The app is correctly installed on the emulator, but does not start up.
I can run and debug this app on USB-Device.
I can run and debug any other app on same emulator.
I tried different AVDs (arm and intel), SDK and Target
Build finishes with 0 errors and 0 warnings. Eventlog is empty. I cleaned the gradle file and changed the only dependency com.android.support:appcompat-v7:21.+.
I can start the app normally on the AVD by clicking on it's icon.
When I start debugging, app installs, then waits endlessly on:
Waiting for process: com.example.myapp
I do not even now where to start looking (of course I tried rebuilding, synchronizing and cleaning cache). I also tried changing the project name.
Maybe try making a new project and copying your code over?