In my test project, I can run my application but cannot debug it, when I run my app the apply changes and restart activity button and apply code changes are disabled and report app not detected.
And in the application window it shows a dialog with below message
application .... is waiting for the debugger to attach.
I tried following:
select app to be debugged
android:debuggable="true" in manifest
In build
debug
{
debuggable true
}
tried adb kill server and restart it
Issue snapshot
You can use
Attach Debugger to Android Process
We have an android app which is composed of two different apps.
Launcher activity is present in 1 project which has a package name
in.foo.android.main.MainActivity
while app package which is shown in uiautomator view is something like
com.abc.android.debug
in desired capabilites I am setting following :
capabilities.setCapability(MobileCapabilityType.APP_PACKAGE ,"com.abc.android.debug");
capabilities.setCapability(MobileCapabilityType.APP_ACTIVITY,"in.foo.android.main.MainActivity");
So getting below error
com.abc.android.debug/in.foo.android.main.MainActivity is not a launchable activity
Here appium is adding package name by default before the main activity.
can someone provide some help here.
First
Go to CMD as admin type adb devices
Make sure that your device already opened the apps that you want
go to cmd and type adb shell dumpsys window | find "mCurrentFocus"
this the exp
Thats command will showing the current activity
Second
Install the APK Info from playstore (idk if you try on the appstore)
https://play.google.com/store/apps/details?id=com.wt.apkinfo&hl=in&gl=US
Open the APK Info
Search your apps s name and click it
You will see this screen
appdetail
Scroll down and check the activities
activities
You will see all of the activity on the apps
existingactivity
Well I just downloaded everything today to get started programming on android. Files Downloaded: Java JRE and JDK, both latest versions. And ADT Bundle (unzipped in a folder).
In the process running "Myfirstapp" I got stuck trying to launch AVD, no idea why it is not working.
(Device: 2.7" QVGA--Target:Android 4.3 - API level 18--default everything else)
After created the new AVD, I clicked start then the launch windows appears and nothing happened, no error message also.
If I try to run the app directly using "run as: Android Application" i got this on the
Cosole:
[2013-11-02 20:26:35 - MySECAPP] ------------------------------
[2013-11-02 20:26:35 - MySECAPP] Android Launch!
[2013-11-02 20:26:35 - MySECAPP] adb is running normally.
[2013-11-02 20:26:35 - MySECAPP] Performing com.example.mysecapp.MainActivity activity launch
[2013-11-02 20:26:41 - MySECAPP] Launching a new emulator with Virtual Device 'NUEVO'
Hi guys I just wanted to say that I solved My problem updating my videocard driver(ATI Radeon HD 5450).
im using eclipse to develop android app.
Im debugging my app on real device, htc desire hd.
When i start my app from eclipse its allways restart my phone.
This behavior wasnt allways like this and suddenly happaned.
I tried 3 different ROMs all 4.2.2 and its happing in all of them.
In my log cat i dont see any errors except this in my console:
[2013-09-05 21:25:33 - WorkoutLog2] Failed to install WorkoutLog2.apk on device 'HT0BRRX047774!
[2013-09-05 21:25:33 - WorkoutLog2] (null)
[2013-09-05 21:25:33 - WorkoutLog2] Launch failed on device: HT0BRRX047774
Why this is happening?
Ok Folks I decided to try this developer thing, and after about a dozen tutorials, ended up with the following Hello World type program:
package com.example.helloandroid;
import android.app.Activity;
import android.os.Bundle;
import android.widget.TextView;
public class HelloAndroid extends Activity {
/** Called when the activity is first created. */
#Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
TextView tv = new TextView(this);
tv.setText("Hello, Android");
setContentView(tv);}
}
Simple enough, So I go to compile it and I get this
[2011-03-14 00:11:25 - HelloAndroid] Android Launch!
[2011-03-14 00:11:25 - HelloAndroid] adb is running normally.
[2011-03-14 00:11:25 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-03-14 00:11:25 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'my_avd'
[2011-03-14 00:11:25 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd'
[2011-03-14 00:11:30 - HelloAndroid] New emulator found: emulator-5554
[2011-03-14 00:11:30 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
Or if I have the emulator already up, I get this
[2011-03-14 08:23:09 - HelloAndroid] Android Launch!
[2011-03-14 08:23:09 - HelloAndroid] adb is running normally.
[2011-03-14 08:23:09 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-03-14 08:23:09 - HelloAndroid] Automatic Target Mode: using existing emulator 'emulator-5554' running compatible AVD 'my_avd'
[2011-03-14 08:23:09 - HelloAndroid] WARNING: Application does not specify an API level requirement!
[2011-03-14 08:23:09 - HelloAndroid] Device API version is 7 (Android 2.1-update1)
[2011-03-14 08:23:09 - HelloAndroid] Uploading HelloAndroid.apk onto device 'emulator-5554'
[2011-03-14 08:23:09 - HelloAndroid] Installing HelloAndroid.apk...
[2011-03-14 08:23:26 - HelloAndroid] Success!
[2011-03-14 08:23:27 - HelloAndroid] Starting activity com.example.helloandroid.HelloAndroid on device emulator-5554
And then the emulator comes up everytime with just this blank screen, with the text "android" on it. And it sits there for about 3 minutes until it goes to another blank black screen with "android" except its animated. I have looked around and can't seem to find anyone who has the same problem. Its like the emulator does not even recognize anything I am doing. Here is a nice screenshot of the blank nothingness:
So, any ideas what I did wrong?
Try waiting for the emulator to load everything before lunching your app.
That's the startup screen for the emulator... It takes a while to boot the emulator, but once it is up and running, it should fire up your application.
The first typed font is the bootstrapping stage, and then the animated version is when it is loading the OS. The next screen should be your Android platform with a GUI.
I too had the same issue.
The program should be executed only after the emulator is ready to run it. So wen u open eclipse press the run button and wait for some time. This will indirectly start the emulator. Once it is loaded press the run button again, this time to run the program.
I had this issue too. My problem was the SDK version. I installed versions 3.1, 3.2 and 2.2 on my Eclipse and I created 3 different target machines. SDK versions 3.1 and 3.2 did not work whereas version 2.2 did go through. I guess there is no stable emulator for SDK 3.*. If you really need to use such a SDK version you might consider using an actual device. My system: Ubuntu 10.04 running Eclipse 3.5.2.
Hope this helps.
when you open the eclipse then go the run tab and run the emulator and appears the GUI screens in emulator then run the application.and then here after use the same emulator dont close.it take a more time to run the emulator. if your system slow.
Try using Genymotion. You can download a version for Windows/Mac OS X/Linux after registering. A plugin for Eclipse is also avaliable.
i give you link Genymotion Emulator please download and setup.
as per my experience Genymotion Vertual device is faster then android emulator.
after you get result
HelloAndroid] Starting activity com.example.helloandroid.HelloAndroid on device emulator-5554
on you console
click on menu button and try to see output