Unable to launch Activity and Wait Activity

Issues/Bugs
1

Original and Current as just same activities in my code, but still I got this error. Any ideas?

debug: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: com.asurion.android.verizon.vms/p.activity.provision.WelcomeScreenActivity never started. Current: com.asurion.android.verizon.vms/com.asurion.android.verizon.vmsp.activity.provision.WelcomeScreenActivity)","origValue":"com.asurion.android.verizon.vms/p.activity.provision.WelcomeScreenActivity never started. Current: com.asurion.android.verizon.vms/com.asurion.android.verizon.vmsp.activity.provision.WelcomeScreenActivity"},"sessionId":null}
1 Like
2

Seems like a bug. My desired capabilities entry is (appPackage/appActivity):

com.asurion.android.verizon.vms/com.asurion.android.verizon.vmsp.activity.provision.WelcomeScreenActivity

But read as:

com.asurion.android.verizon.vms/p.activity.MainActivity

ERROR:

debug: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: com.asurion.android.verizon.vms/p.activity.MainActivity never started. Current: com.asurion.android.verizon.vms/com.asurion.android.verizon.vmsp.activity.provision.WelcomeScreenActivity)","origValue":"com.asurion.android.verizon.vms/p.activity.MainActivity never started. Current: com.asurion.android.verizon.vms/com.asurion.android.verizon.vmsp.activity.provision.WelcomeScreenActivity"},"sessionId":null}

I think it asumes that I forgot the slash.

3

I’m having trouble understanding the issue exactly. Can you post the desired caps you are using exactly?

4 
DesiredCapabilities capabilities = new DesiredCapabilities();       capabilities.setCapability("platformName", "Android"); capabilities.setCapability("platformVersion", "4.4" );      capabilities.setCapability("deviceName", "Android");           capabilities.setCapability("appPackage", "com.asurion.android.verizon.vms");             capabilities.setCapability("appActivity", "com.asurion.android.verizon.vmsp.activity.MainActivity");             capabilities.setCapability("appWaitActivity", com.asurion.android.verizon.vmsp.activity.provision.WelcomeScreenActivity");      return new RemoteWebDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);

Upon checking the appium log activity, I got an error above (previous post). I suspect that the appPackage and appActivity has the same prefix (ie. com.asurion.android.verizon.vms), then Appium read it as :

com.asurion.android.verizon.vms/p.activity.MainActivity

This desired cap works well with other apps with different naming conventions on appPackage and appActivity.

5

You should open a bug on GitHub.

6

Hi Jonah,

Did you get a chance to take a look at this error? We are having the correct activity names but still getting the same error, please help here.

Thanks

7

Did you open an issue on GitHub?

8

I’ve opened a bug in Github:

9

I know i’m bumping a really old thread.
But i’m having this same problem with appium 1.3.7
Specifically:
–no-reset = true
2nd test fails. first test is ok.

I’ve added to this in github. Let me know if there’s something obvious i’m doing wrong.
Thanks!

10

false alarm.
I figured out my problem. I needed to add this in my caps
appWaitActivity = “com.blackboard.android.bblearn.login.activity.LoginActivity”

thanks
Eric