Chrome welcome window on Android 13 emulator

Issues/Bugs
1

Hi Team,

While running Android-13 emulator with Test Suite we are getting Chrome’s welcome window.
I did tried with various Appium capabilities mentioned below, but the results are same.
Any help would be highly appreciated.
I already went through older posts on the community forum and stackoverflow none of them helped so far.

Looking forward to a positive response from the community.
Capabilities I have tried so far:

“appPackage”: “com.android.chrome”,
“appActivity”: “com.google.android.apps.chrome.Main”,
“intentCategory”: “android.intent.category.LAUNCHER”,
“intentAction”: “android.intent.action.MAIN”,

32%20PM
Screenshot 2022-10-04 at 2.06.32 PM.jpg2880×1800 158 KB
57%20PM
Screenshot 2022-10-04 at 2.12.57 PM.jpg2880×1800 174 KB

2
1 Like
3

@mykola-mokhnach , curious now, what does the disable-fre flag mean, as in what does fre stand for?

4

Thanks @mykola-mokhnach for the response.
But sadly the disabling welcome screen via ChromeOption didn’t help either.
Welcome screen is still visible.

The capability in use are:
“appPackage”: “com.android.chrome”,
“appActivity”: “com.google.android.apps.chrome.Main”,
“intentCategory”: “android.intent.category.LAUNCHER”,
“intentAction”: “android.intent.action.MAIN”,
“chromeOptions”: {
“args”: ["–disable-fre"]
}

I did tried the capability mentioned by you at: https://github.com/appium/appium/issues/6618#issuecomment-228772718

But still unable to resolve it.

Any suggestions from your side will be highly appreciated.

Many Thanks
Ganesh Sharma

5

Such behaviour is expected. chrome options are applied to chromedriver, although no chromedriver is used according to the above capabilities. Read https://github.com/appium/appium-uiautomator2-driver#hybrid-mode

1 Like
6

Hi @mykola-mokhnach

I did tried to use the capabilities mentioned above, but the results are still negative.
Any suggestions from your end will be very helpful.

Capabilities with which I have played around is below:

            "appPackage": "com.android.chrome",
            "appActivity": "com.google.android.apps.chrome.Main",
            "chromeOptions": {
                "args": ["--disable-fre"]
            },
            "chromedriverUseSystemExecutable": False,
            "chrome_options.chromedriver_executable": '/root/lambda/shared-tools/volume/drivers/chromedriver/101.0',
            #"chromedriverChromeMappingFile": "/root/lambda/shared-tools/volume/appium/appium-1.22.3/node_modules/appium-chromedriver/config/mapping.json",
            #"chromedriverExecutableDir": "/root/lambda/shared-tools/volume/drivers/chromedriver",
            #"chromedriverExecutable": "/root/lambda/shared-tools/volume/drivers/chromedriver/101.0",
            "intentCategory": "android.intent.category.LAUNCHER",
            "intentAction": "android.intent.action.MAIN",
7

if an option has a typo or is in the wrong place in the structure, the appium logs will “sometimes” tell you near the top that it was ignored, i assume you read the log