Set ChromeOptions with androidProcess in DesiredCapabilities will raise error

[megolee]

Description

Set DediredCapabilities with androidProcess in ChromeOptions as below:

DesiredCapabilities desired_capabilities = new DesiredCapabilities(); desired_capabilities.setCapability(AndroidMobileCapabilityType.PLATFORM, "Android"); desired_capabilities.setCapability(AndroidMobileCapabilityType.VERSION, "6.0"); desired_capabilities.setCapability("deviceName", "Android"); desired_capabilities.setCapability(AndroidMobileCapabilityType.APP_PACKAGE, "com.tencent.mm"); desired_capabilities.setCapability(AndroidMobileCapabilityType.APP_ACTIVITY, "ui.LauncherUI"); desired_capabilities.setCapability("showChromedriverLog", true); desired_capabilities.setCapability(AndroidMobileCapabilityType.AUTO_GRANT_PERMISSIONS, true); desired_capabilities.setCapability("noReset", true); ChromeOptions chrome_options = new ChromeOptions(); chrome_options.setExperimentalOption("androidProcess", "com.tencent.mm:tools"); desired_capabilities.setCapability(ChromeOptions.CAPABILITY, chrome_options);

When try to launch driver, appium will give the Error: Could not find package com.android.chrome on the device

This error happened with java client 6.0.0, but it is ok with 5.0.0

Environment

• java client build version or git revision if you use some shapshot: 6.0.0
• Appium server version or git revision if you use some shapshot: 1.8.1
• Desktop OS/version used to run Appium if necessary: Mac High Sierra
• Node.js version (unless using Appium.app|exe) or Appium CLI or Appium.app|exe: 10.1.0
• Mobile platform/version under test: Android 6.0
• Real device or emulator/simulator: emulator

Details

Please provide more details, if necessary.

Code To Reproduce Issue [ Good To Have ]

Ecxeption stacktraces

https://gist.github.com/megolee/9e010f6efb7d9572494cbb3fd4c00061

Link to Appium logs

java client 6.0.0: https://gist.github.com/megolee/8d9c4dd279d70e34dd5934c0e9886ce8

java client 5.0.0: https://gist.github.com/megolee/60d9b9746531343bea886ae1e4757c7c

[mykola-mokhnach]

The capabilities are incorrect. One can either set browser name or app activity but not both

[megolee]

@mykola-mokhnach The capabilities works on both java client 5.0.0 and latest python client, why it is incorrect for java client 6.0.0?

Since the app I tested is a hybird app, and the weview is running on a different process rather than the native view. So I have to set the chrome_options with androidProcess, otherwise appium cannot switch to the webview. Is there any workround?

Many Thanks.

[mykola-mokhnach]

Check appium/appium#10970. Perhaps the problem, which is described there, is similar to yours.

[megolee]

Still not working

[roosto]

@megolee Have you had a look at this issue: appium/appium#8958 ?

I think that it might be relevant to your struggles.

[megolee]

@SrinivasanTarget Why this issue closed? It still happens.

[SrinivasanTarget]

@megolee Can you check in latest appium server and java client (from latest master commit) and update the logs here. Also try setting capability forceMjsonwp to true and give a try.

[megolee]

Java Client Latest Commit
@SrinivasanTarget Hi, this is the log with java client latest commit and appium 1.9.1@beta2, appium through an error when session create. I have also tried with the same code and env only change the java client to 5.0.0, java client 5.0.0 still working.

[megolee]

Seems that the desired capabilities will take the browserName:chrome automatic, as I didn't define this capability in the code. But the appium logs say it need appPackage or browserName.

https://gist.github.com/megolee/a7e916d1ac0abb875b31ff6287aeac29#file-java-client-last-commit-L24

https://gist.github.com/megolee/a7e916d1ac0abb875b31ff6287aeac29#file-java-client-last-commit-L31

[saikrishna321]

@megolee https://gist.github.com/megolee/a7e916d1ac0abb875b31ff6287aeac29#file-java-client-last-commit-L4

i see you have given browserName: chrome

[megolee]

@SrinivasanTarget I didn't give browserName: chrome in my code, below is my code.

Actually, when I use java client 6.0.0 or the latest commit, it will take the browserName:chrome automatic. But when I roll back to 5.0.0, browserName:chrome does not appear in the logs.

`import java.net.MalformedURLException;
import java.net.URL;

import org.openqa.selenium.chrome.ChromeOptions;
import org.openqa.selenium.remote.DesiredCapabilities;

import io.appium.java_client.android.AndroidDriver;
import io.appium.java_client.android.AndroidElement;
import io.appium.java_client.remote.AndroidMobileCapabilityType;
import io.appium.java_client.remote.MobileCapabilityType;

public class JavaSimple {

public static AndroidDriver<AndroidElement> driver;

public static void main(String[] args) {

	DesiredCapabilities desired_capabilities = new DesiredCapabilities();
	desired_capabilities.setCapability(AndroidMobileCapabilityType.PLATFORM, "Android");
	desired_capabilities.setCapability(AndroidMobileCapabilityType.VERSION, "6.0");
	desired_capabilities.setCapability("deviceName", "Android");
	desired_capabilities.setCapability(MobileCapabilityType.FORCE_MJSONWP, true);
	desired_capabilities.setCapability(AndroidMobileCapabilityType.APP_PACKAGE, "com.tencent.mm");
	desired_capabilities.setCapability(AndroidMobileCapabilityType.APP_ACTIVITY, "ui.LauncherUI");
	desired_capabilities.setCapability("showChromedriverLog", true);
	desired_capabilities.setCapability(AndroidMobileCapabilityType.AUTO_GRANT_PERMISSIONS, true);
	desired_capabilities.setCapability("noReset", true);
	ChromeOptions chrome_options = new ChromeOptions();
	chrome_options.setExperimentalOption("androidProcess", "com.tencent.mm:tools");
	desired_capabilities.setCapability(ChromeOptions.CAPABILITY, chrome_options);
	
	try {
		driver = new AndroidDriver<>(new URL("http://127.0.0.1:4723/wd/hub"),desired_capabilities);
	} catch (MalformedURLException e) {
		e.printStackTrace();
	}
	

}

}`

[saikrishna321]

@megolee just curious why do u have this in your caps

ChromeOptions chrome_options = new ChromeOptions();
	chrome_options.setExperimentalOption("androidProcess", "com.tencent.mm:tools");
	desired_capabilities.setCapability(ChromeOptions.CAPABILITY, chrome_options);

[megolee]

@saikrishna321 As the web view of the app is running on an independent process rather than the native view. So I have to set the chrome_options with androidProcess, otherwise appium cannot switch to the web view.