Activity used to start app doesn’t exist or cannot be launched! Make sure it exists and is a launchable activity

Hi @Aleksei, thanks for the fast answer!

I tried what you suggested, even left the “appActivity” line with no luck at all!

Please let me know anything you need from my side to try to figure this out.

Cheers,

Juan

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

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");

@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!

@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, sure thing I can try that!

@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, hi there!

Sorry to bother you but did you get a chance to look at my last msg?

Thanks in advance for your time!

@Aleksei

First option worked! Thanks a lot for all your help! We can consider this ticket Solved.

Cheers!!