This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
Aug 2017
9 / 24
Aug 2017
Feb 2019
juanmartinvidal
Aug '17

Hi @Aleksei, thanks for getting back to me.

Here’s the gist15 with the complete Log from Appium since I started the server.

Let me know if there’s anything else you need from my side.

And in my MANIFEST11 in the Android app this is my main activity.

Aleksei
Aug '17

@juanmartinvidal

  1. remove “appPackage” (it will get from apk automatically) and “appActivity” (this is needed when you start existing app on phone)
  2. add:
capabilities.setCapability(AndroidMobileCapabilityType.APP_WAIT_ACTIVITY, ".activities.MainActivity");
// or
capabilities.setCapability("appWaitActivity", ".activities.MainActivity");

if it fails check appium logs again to see what activity started instead

SO! total once again:

capabilities.setCapability("automationName", "Appium"); // can be values "Appium", "Selendroid", "XCuiTest", "UIAutomator2", "espresso"
capabilities.setCapability("platformVersion", "5.5");
capabilities.setCapability("deviceName", "nexus_5x");
capabilities.setCapability("avd", "nexus_5x");
capabilities.setCapability("app", "C:\\Users\\juanvidal\\projects\\automation\\src\\test\\resources\\apps\\tu-admin.apk");
capabilities.setCapability("appWaitActivity", ".activities.MainActivity");
capabilities.setCapability("platformName", "Android");
capabilities.setCapability(AndroidMobileCapabilityType.AUTO_GRANT_PERMISSIONS, "true"); //valid from Android 6.0
juanmartinvidal
Aug '17

@Aleksei

With your last suggestions now it starts up the app and I was able to login in my VM.

In the logs it says [ADB] Found package: 'com.jcor.tuadmin' and fully qualified activity name : 'com.jcor.laadministracion.activities.ListUserFunctionalUnitActivity'

and because it doesn’t find the MainActivity it shuts down.

Aleksei
Aug '17

@juanmartinvidal so the only change now is:

capabilities.setCapability("appWaitActivity", ".activities.ListUserFunctionalUnitActivity");
// or try
capabilities.setCapability("appWaitActivity", ".activities.*");
juanmartinvidal
Aug '17

@Aleksei

Exactly, this is what I have now:

//Configurable properties
capabilities.setCapability(“platformVersion”, “5.5”);
capabilities.setCapability(“deviceName”, “nexus_5x”);
capabilities.setCapability(“avd”, “nexus_5x”);
capabilities.setCapability(“app”, “C:\Users\juanvidal\projects\automation\src\test\resources\apps\tu-admin.apk”);
capabilities.setCapability(“appWaitActivity”, “.activities.ListUserFunctionalUnitActivity”);

    //Fixed Properties
    capabilities.setCapability("platformName", "Android");
    capabilities.setCapability("automationName", "Appium");
    capabilities.setCapability("appium-version", "1.6");

This is what I had:

//Configurable properties
capabilities.setCapability(“platformVersion”, “5.5”);
capabilities.setCapability(“deviceName”, “nexus_5x”);
capabilities.setCapability(“avd”, “nexus_5x”);
capabilities.setCapability(“app”, “C:\Users\juanvidal\projects\automation\resources\apps\flipkart.apk”);
capabilities.setCapability(“appPackage”, “com.flipkart.android”);
capabilities.setCapability(“appActivity”, “com.flipkart.android.SplashActivity”);

    //Fixed Properties
    capabilities.setCapability("appium-version", "1.6");
    capabilities.setCapability("platformName", "Android");
juanmartinvidal
Aug '17

@Aleksei

Actually the initial problem was solved because now my VM loads my apk and shows the Login Page. I manually login and so far so good, but in Appium I see the error I mentioned before [ADB] Found package: 'com.jcor.tuadmin' and fully qualified activity name : 'com.jcor.laadministracion.activities.ListUserFunctionalUnitActivity' and it stops the app in the VM.

I tried changing the config to point to that Activity instead of the MainActivity one but no luck, same error.

Thanks!

juanmartinvidal
Aug '17

@Aleksei,

that didn’t help either. I think I found the error but I wanted to hear your thoughs.

With .activities.* or with .activities.MainActivity I get an error like this in Appium before it shuts down the app in the VM: [MJSONWP] Encountered internal error running command: Error: Error occured while starting App. Original error: com.jcor.tuadmin.activities.* never started

So in the original package name was com.jcor.laadministracion and then we changed it in the configuration files but not in the code itself.

If I add the appPackage capability to set the right package name it fails with the old error.

Could it be that the only fix here is to match the configuration package name with the actual code package name??

Aleksei
Aug '17

@juanmartinvidal may you just connect to android studio with phone. start client and check what full package name + activity starting? e.g. when i am starting “Contacts” on mine LG G4 i have message like:

08-15 16:00:31.141 1474-3484/? I/ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.contacts/.activities.DialtactsActivity bnds=[0,2128][288,2392]} from uid 10053 on display 0

where i have “com.android.contacts” package name, “.activities.DialtactsActivity” activity started

juanmartinvidal
Aug '17

@Aleksei

Got the info for you:

08-15 10:33:13.304 898-1279/? I/ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.jcor.tuadmin/com.jcor.laadministracion.activities.MainActivity} from uid 2000 on display 0

That shows exactly what I was trying to explain. The real package in the source code is com.jcor.laadministracion while in the config files is com.jcor.tuadmin

Aleksei
Aug '17

@juanmartinvidal did you try with:

capabilities.setCapability("appWaitActivity", "com.jcor.laadministracion.activities.MainActivity");
// or
capabilities.setCapability("appWaitActivity", "com.jcor.laadministracion.activities.*");
// or maybe even
capabilities.setCapability("appWaitActivity", "*");

?

1 year later
mark.tumanow
Feb '19

Hello guys,

I need your help. Seems a similar issue but no success for me doing things which was usefull for @juanmartinvidal .

So Error is: “Original error: Cannot start the ‘com.oneonone.boxvpn’ application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: Cannot start the ‘com.oneonone.boxvpn’ application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: Activity name ‘.boxpn.gtcap.co.uk.react_vpn.SplashActivity’ used to start the app doesn’t exist or cannot be launched! Make sure it exists and is a launchable activity”

I have used following code in capabilities:

capabilities.setCapability("platformName", "Android");
capabilities.setCapability(MobileCapabilityType.DEVICE_NAME, "Demo");
capabilities.setCapability(MobileCapabilityType.APP, app.getAbsolutePath());
capabilities.setCapability(MobileCapabilityType.APPIUM_VERSION, "1.10.1");
driver = new AndroidDriver<>(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);
capabilities.setCapability("appWaitPackage", "com.oneonone.boxvpn");
capabilities.setCapability("appWaitActivity", "*");

Also I have used different cases for “appWaitActivity”:
capabilities.setCapability(“appWaitActivity”, “.boxpn.gtcap.co.uk.react_vpn.SplashActivity”); OR
capabilities.setCapability(“appWaitActivity”, “boxpn.gtcap.co.uk.react_vpn.SplashActivity”); OR
capabilities.setCapability(“appWaitActivity”, “.boxpn.gtcap.co.uk.react_vpn.MainActivity”); OR
capabilities.setCapability(“appWaitActivity”, “boxpn.gtcap.co.uk.react_vpn.MainActivity”); OR
capabilities.setCapability(“appWaitActivity”, “.SplashActivity"); OR
capabilities.setCapability(“appWaitActivity”, ".MainActivity”); OR

Nothing from listed strings didn’t works. Please let me know if you have any ideas or things I can try to invoke an app.