[chromium-dev] Skipping "Welcome to Chrome"

[Eric Savoie]

I'm trying to run some automated tests and the "Welcome to Chrome" pop up is being rather troublesome. I've attempted to add flags to skip it with adb shell --no-first-run and --disable-fre but neither of the flags actually got set.

My env is OS X running protractor with appium and an Android emulator. The tests run fine but I am finding myself unable to do anything but manually click the welcome modal. I've used at least one to two pages of suggestions on 10 hours of semi-creative googling. I'm hoping most answers are just outdated.

[David Roger]

These flags look fine. I checked in one of our scripts, and it uses:
--disable-fre --no-default-browser-check --no-first-run

There are instructions how to set command line flags on Android here:
https://www.chromium.org/developers/how-tos/run-chromium-with-flags

If you need to do this in a python script, I think you can use FlagChanger:
https://cs.chromium.org/chromium/src/third_party/catapult/devil/devil/android/flag_changer.py?q=FlagChanger&sq=package:chromium&l=12&dr=CSs

Post by Eric Savoie
I'm trying to run some automated tests and the "Welcome to Chrome" pop up
is being rather troublesome. I've attempted to add flags to skip it with
adb shell --no-first-run and --disable-fre but neither of the flags
actually got set.
My env is OS X running protractor with appium and an Android emulator. The
tests run fine but I am finding myself unable to do anything but manually
click the welcome modal. I've used at least one to two pages of suggestions
on 10 hours of semi-creative googling. I'm hoping most answers are just
outdated.
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev

[Eric Savoie]

<Loading Image...>

Looks like it was already running as root... the mystery deepens.

<Loading Image...>

Can't seem to make it work :(

Post by Eric Savoie
I'm trying to run some automated tests and the "Welcome to Chrome" pop up
is being rather troublesome. I've attempted to add flags to skip it with
adb shell --no-first-run and --disable-fre but neither of the flags
actually got set.
My env is OS X running protractor with appium and an Android emulator. The
tests run fine but I am finding myself unable to do anything but manually
click the welcome modal. I've used at least one to two pages of suggestions
on 10 hours of semi-creative googling. I'm hoping most answers are just
outdated.

[PhistucK]

Hmm are you running Content Shell or Android WebView?
If not, you want to use instead (or in addition) -
/data/local/tmp/chrome-command-line
/data/local/chrome-command-line

See https://cs.chromium.org/chromium/src/build/android/
adb_chrome_public_command_line?q=adb_chrome_public_command_line&sq=package:
chromium&dr=C&l=21.


☆*PhistucK*

Post by Eric Savoie
<https://lh3.googleusercontent.com/-xnGu12vdA88/WAYdrO5wcmI/AAAAAAAAAGU/l7G0jZSEsPE2vHVmbgGl0PNXKedGf6VOgCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.02.20%2BAM.png>
Looks like it was already running as root... the mystery deepens.
<https://lh3.googleusercontent.com/-Sl5PJeGz5QA/WAYfRsrfEKI/AAAAAAAAAGY/z50N9PLs_0Yz9wjtH2-Fjx6rpPoh8h9gQCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.09.41%2BAM.png>
Can't seem to make it work :(

Post by Eric Savoie
I'm trying to run some automated tests and the "Welcome to Chrome" pop up
is being rather troublesome. I've attempted to add flags to skip it with
adb shell --no-first-run and --disable-fre but neither of the flags
actually got set.
My env is OS X running protractor with appium and an Android emulator.
The tests run fine but I am finding myself unable to do anything but
manually click the welcome modal. I've used at least one to two pages of
suggestions on 10 hours of semi-creative googling. I'm hoping most answers
are just outdated.

--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an

[Eric Savoie]

I downgraded my AVD to Marshmellow (6.0) and I got an interesting line that
I wasn't getting with 7.0. Additionally it looks like 7.0 is extremely hard
to get root access on.

[100%]
/data/local/tmp/com.android.chrome_53.0.2785.124-278512411_minAPI21x86nodpi_apkmirror.com.apk

pkg:
/data/local/tmp/com.android.chrome_53.0.2785.124-278512411_minAPI21x86nodpi_apkmirror.com.apk

Is the message I got from I added chrome to my Galaxy Nexus with Android
6.0.

However the adb shell commands did not work.

How do I check which one I am supposed to be using? I tried all three.

Post by PhistucK
Hmm are you running Content Shell or Android WebView?
If not, you want to use instead (or in addition) -
/data/local/tmp/chrome-command-line
/data/local/chrome-command-line
See
https://cs.chromium.org/chromium/src/build/android/adb_chrome_public_command_line?q=adb_chrome_public_command_line&sq=package:chromium&dr=C&l=21
.
☆*PhistucK*

Post by Eric Savoie
<https://lh3.googleusercontent.com/-xnGu12vdA88/WAYdrO5wcmI/AAAAAAAAAGU/l7G0jZSEsPE2vHVmbgGl0PNXKedGf6VOgCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.02.20%2BAM.png>
Looks like it was already running as root... the mystery deepens.
<https://lh3.googleusercontent.com/-Sl5PJeGz5QA/WAYfRsrfEKI/AAAAAAAAAGY/z50N9PLs_0Yz9wjtH2-Fjx6rpPoh8h9gQCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.09.41%2BAM.png>
Can't seem to make it work :(

Post by Eric Savoie
I'm trying to run some automated tests and the "Welcome to Chrome" pop
up is being rather troublesome. I've attempted to add flags to skip it with
adb shell --no-first-run and --disable-fre but neither of the flags
actually got set.
My env is OS X running protractor with appium and an Android emulator.
The tests run fine but I am finding myself unable to do anything but
manually click the welcome modal. I've used at least one to two pages of
suggestions on 10 hours of semi-creative googling. I'm hoping most answers
are just outdated.

--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an

[Eric Savoie]

Well great news. I don't know what did it but the welcome screen has gone
away using Galaxy Nexus 6 with nothing else changed. Maybe the
"chromeOptions" in protractor are incompatible with 6+. Thanks for the help
guys.

Post by Eric Savoie
I downgraded my AVD to Marshmellow (6.0) and I got an interesting line
that I wasn't getting with 7.0. Additionally it looks like 7.0 is extremely
hard to get root access on.
[100%]
/data/local/tmp/com.android.chrome_53.0.2785.124-278512411_minAPI21x86nodpi_apkmirror.com.apk
/data/local/tmp/com.android.chrome_53.0.2785.124-278512411_minAPI21x86nodpi_apkmirror.com.apk
Is the message I got from I added chrome to my Galaxy Nexus with Android
6.0.
However the adb shell commands did not work.
How do I check which one I am supposed to be using? I tried all three.

Post by PhistucK
Hmm are you running Content Shell or Android WebView?
If not, you want to use instead (or in addition) -
/data/local/tmp/chrome-command-line
/data/local/chrome-command-line
See
https://cs.chromium.org/chromium/src/build/android/adb_chrome_public_command_line?q=adb_chrome_public_command_line&sq=package:chromium&dr=C&l=21
.
☆*PhistucK*

Post by Eric Savoie
<https://lh3.googleusercontent.com/-xnGu12vdA88/WAYdrO5wcmI/AAAAAAAAAGU/l7G0jZSEsPE2vHVmbgGl0PNXKedGf6VOgCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.02.20%2BAM.png>
Looks like it was already running as root... the mystery deepens.
<https://lh3.googleusercontent.com/-Sl5PJeGz5QA/WAYfRsrfEKI/AAAAAAAAAGY/z50N9PLs_0Yz9wjtH2-Fjx6rpPoh8h9gQCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.09.41%2BAM.png>
Can't seem to make it work :(

Post by Eric Savoie
I'm trying to run some automated tests and the "Welcome to Chrome" pop
up is being rather troublesome. I've attempted to add flags to skip it with
adb shell --no-first-run and --disable-fre but neither of the flags
actually got set.
My env is OS X running protractor with appium and an Android emulator.
The tests run fine but I am finding myself unable to do anything but
manually click the welcome modal. I've used at least one to two pages of
suggestions on 10 hours of semi-creative googling. I'm hoping most answers
are just outdated.

--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google
Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send

[Ilya]

In case this helps someone else, I was trying to change the command line to
no avail in Android 7.1.1

After running with -show-kernel -verbose, it turned out that the selinux
was preventing chrome from reading from /data/local/chrome-command-line
It worked after running with "-selinux disabled"

I was able to finally launch Chrome with a custom command line by using:

adb shell 'echo "chrome --no-default-browser-check --no-first-run
--disable-fre" > /data/local/chrome-command-line'

adb shell am start -n
com.android.chrome/com.google.android.apps.chrome.Main -d "$URL"

after running the emulator with "emulator ... -selinux disabled"

Hope this helps someone else trying to do this!

Post by Eric Savoie
Well great news. I don't know what did it but the welcome screen has gone
away using Galaxy Nexus 6 with nothing else changed. Maybe the
"chromeOptions" in protractor are incompatible with 6+. Thanks for the help
guys.

Post by Eric Savoie
I downgraded my AVD to Marshmellow (6.0) and I got an interesting line
that I wasn't getting with 7.0. Additionally it looks like 7.0 is extremely
hard to get root access on.
[100%]
/data/local/tmp/com.android.chrome_53.0.2785.124-278512411_minAPI21x86nodpi_apkmirror.com.apk
/data/local/tmp/com.android.chrome_53.0.2785.124-278512411_minAPI21x86nodpi_apkmirror.com.apk
Is the message I got from I added chrome to my Galaxy Nexus with Android
6.0.
However the adb shell commands did not work.
How do I check which one I am supposed to be using? I tried all three.

Post by PhistucK
Hmm are you running Content Shell or Android WebView?
If not, you want to use instead (or in addition) -
/data/local/tmp/chrome-command-line
/data/local/chrome-command-line
See
https://cs.chromium.org/chromium/src/build/android/adb_chrome_public_command_line?q=adb_chrome_public_command_line&sq=package:chromium&dr=C&l=21
.
☆*PhistucK*

Post by Eric Savoie
<https://lh3.googleusercontent.com/-xnGu12vdA88/WAYdrO5wcmI/AAAAAAAAAGU/l7G0jZSEsPE2vHVmbgGl0PNXKedGf6VOgCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.02.20%2BAM.png>
Looks like it was already running as root... the mystery deepens.
<https://lh3.googleusercontent.com/-Sl5PJeGz5QA/WAYfRsrfEKI/AAAAAAAAAGY/z50N9PLs_0Yz9wjtH2-Fjx6rpPoh8h9gQCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.09.41%2BAM.png>
Can't seem to make it work :(

Post by Eric Savoie
I'm trying to run some automated tests and the "Welcome to Chrome" pop
up is being rather troublesome. I've attempted to add flags to skip it with
adb shell --no-first-run and --disable-fre but neither of the flags
actually got set.
My env is OS X running protractor with appium and an Android emulator.
The tests run fine but I am finding myself unable to do anything but
manually click the welcome modal. I've used at least one to two pages of
suggestions on 10 hours of semi-creative googling. I'm hoping most answers
are just outdated.

--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google
Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send

[Torne (Richard Coles)]

You should write the command line to /data/local/tmp instead which isn't
blocked by selinux. There's a bug open about switching this over completely
in all scripts and docs but we haven't quite sorted it yet.

Post by Ilya
In case this helps someone else, I was trying to change the command line
to no avail in Android 7.1.1
After running with -show-kernel -verbose, it turned out that the selinux
was preventing chrome from reading from /data/local/chrome-command-line
It worked after running with "-selinux disabled"
adb shell 'echo "chrome --no-default-browser-check --no-first-run
--disable-fre" > /data/local/chrome-command-line'
adb shell am start -n
com.android.chrome/com.google.android.apps.chrome.Main -d "$URL"
after running the emulator with "emulator ... -selinux disabled"
Hope this helps someone else trying to do this!
Well great news. I don't know what did it but the welcome screen has gone
away using Galaxy Nexus 6 with nothing else changed. Maybe the
"chromeOptions" in protractor are incompatible with 6+. Thanks for the help
guys.
I downgraded my AVD to Marshmellow (6.0) and I got an interesting line
that I wasn't getting with 7.0. Additionally it looks like 7.0 is extremely
hard to get root access on.
[100%]
/data/local/tmp/com.android.chrome_53.0.2785.124-278512411_minAPI21x86nodpi_apkmirror.com.apk
/data/local/tmp/com.android.chrome_53.0.2785.124-278512411_minAPI21x86nodpi_apkmirror.com.apk
Is the message I got from I added chrome to my Galaxy Nexus with Android
6.0.
However the adb shell commands did not work.
How do I check which one I am supposed to be using? I tried all three.
Hmm are you running Content Shell or Android WebView?
If not, you want to use instead (or in addition) -
/data/local/tmp/chrome-command-line
/data/local/chrome-command-line
See
https://cs.chromium.org/chromium/src/build/android/adb_chrome_public_command_line?q=adb_chrome_public_command_line&sq=package:chromium&dr=C&l=21
.
☆*PhistucK*
<https://lh3.googleusercontent.com/-xnGu12vdA88/WAYdrO5wcmI/AAAAAAAAAGU/l7G0jZSEsPE2vHVmbgGl0PNXKedGf6VOgCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.02.20%2BAM.png>
Looks like it was already running as root... the mystery deepens.
<https://lh3.googleusercontent.com/-Sl5PJeGz5QA/WAYfRsrfEKI/AAAAAAAAAGY/z50N9PLs_0Yz9wjtH2-Fjx6rpPoh8h9gQCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.09.41%2BAM.png>
Can't seem to make it work :(
I'm trying to run some automated tests and the "Welcome to Chrome" pop up
is being rather troublesome. I've attempted to add flags to skip it with
adb shell --no-first-run and --disable-fre but neither of the flags
actually got set.
My env is OS X running protractor with appium and an Android emulator. The
tests run fine but I am finding myself unable to do anything but manually
click the welcome modal. I've used at least one to two pages of suggestions
on 10 hours of semi-creative googling. I'm hoping most answers are just
outdated.
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/b7886020-fb3a-4876-8fbe-ebe53b25d752%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/b7886020-fb3a-4876-8fbe-ebe53b25d752%40chromium.org?utm_medium=email&utm_source=footer>
.

[Ilya Kreymer]

I tried writing to both paths initially, but looks like the /tmp path is
currently only used if Chrome is the debug app:
https://chromium.googlesource.com/chromium/src/+/12bfc336/chrome/android/java/src/org/chromium/chrome/browser/ChromeCommandLineInitUtil.java#66

I don't actually want to debug Chrome, just launch it. But perhaps it
should always check the /tmp path first, even when its not the debug app?

Post by Torne (Richard Coles)
You should write the command line to /data/local/tmp instead which isn't
blocked by selinux. There's a bug open about switching this over completely
in all scripts and docs but we haven't quite sorted it yet.

Post by Ilya
In case this helps someone else, I was trying to change the command line
to no avail in Android 7.1.1
After running with -show-kernel -verbose, it turned out that the selinux
was preventing chrome from reading from /data/local/chrome-command-line
It worked after running with "-selinux disabled"
adb shell 'echo "chrome --no-default-browser-check --no-first-run
--disable-fre" > /data/local/chrome-command-line'
adb shell am start -n com.android.chrome/com.google.android.apps.chrome.Main
-d "$URL"
after running the emulator with "emulator ... -selinux disabled"
Hope this helps someone else trying to do this!
Well great news. I don't know what did it but the welcome screen has gone
away using Galaxy Nexus 6 with nothing else changed. Maybe the
"chromeOptions" in protractor are incompatible with 6+. Thanks for the help
guys.
I downgraded my AVD to Marshmellow (6.0) and I got an interesting line
that I wasn't getting with 7.0. Additionally it looks like 7.0 is extremely
hard to get root access on.
[100%] /data/local/tmp/com.android.chrome_53.0.2785.124-
278512411_minAPI21x86nodpi_apkmirror.com.apk
pkg: /data/local/tmp/com.android.chrome_53.0.2785.124-
278512411_minAPI21x86nodpi_apkmirror.com.apk
Is the message I got from I added chrome to my Galaxy Nexus with Android
6.0.
However the adb shell commands did not work.
How do I check which one I am supposed to be using? I tried all three.
Hmm are you running Content Shell or Android WebView?
If not, you want to use instead (or in addition) -
/data/local/tmp/chrome-command-line
/data/local/chrome-command-line
See https://cs.chromium.org/chromium/src/build/android/
adb_chrome_public_command_line?q=adb_chrome_public_
command_line&sq=package:chromium&dr=C&l=21.
☆*PhistucK*
<https://lh3.googleusercontent.com/-xnGu12vdA88/WAYdrO5wcmI/AAAAAAAAAGU/l7G0jZSEsPE2vHVmbgGl0PNXKedGf6VOgCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.02.20%2BAM.png>
Looks like it was already running as root... the mystery deepens.
<https://lh3.googleusercontent.com/-Sl5PJeGz5QA/WAYfRsrfEKI/AAAAAAAAAGY/z50N9PLs_0Yz9wjtH2-Fjx6rpPoh8h9gQCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.09.41%2BAM.png>
Can't seem to make it work :(
I'm trying to run some automated tests and the "Welcome to Chrome" pop up
is being rather troublesome. I've attempted to add flags to skip it with
adb shell --no-first-run and --disable-fre but neither of the flags
actually got set.
My env is OS X running protractor with appium and an Android emulator.
The tests run fine but I am finding myself unable to do anything but
manually click the welcome modal. I've used at least one to two pages of
suggestions on 10 hours of semi-creative googling. I'm hoping most answers
are just outdated.
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/
chromium.org/d/msgid/chromium-dev/b7886020-fb3a-4876-8fbe-
ebe53b25d752%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/b7886020-fb3a-4876-8fbe-ebe53b25d752%40chromium.org?utm_medium=email&utm_source=footer>
.

[Torne (Richard Coles)]

That's a very old version of the code you linked to; it's from over two
years ago. The current version has for some time checked /data/local/tmp on
all debug builds of the OS regardless of the debug app setting. So, if you
have a userdebug/eng build of Android it should work fine. If you have a
user build, then it does still need to be set as the debug application and
this is intentional; the command line file is only intended to be used for
dev/test/debug purposes.

Post by Ilya Kreymer
I tried writing to both paths initially, but looks like the /tmp path is
https://chromium.googlesource.com/chromium/src/+/12bfc336/chrome/android/java/src/org/chromium/chrome/browser/ChromeCommandLineInitUtil.java#66
I don't actually want to debug Chrome, just launch it. But perhaps it
should always check the /tmp path first, even when its not the debug app?
You should write the command line to /data/local/tmp instead which isn't
blocked by selinux. There's a bug open about switching this over completely
in all scripts and docs but we haven't quite sorted it yet.
In case this helps someone else, I was trying to change the command line
to no avail in Android 7.1.1
After running with -show-kernel -verbose, it turned out that the selinux
was preventing chrome from reading from /data/local/chrome-command-line
It worked after running with "-selinux disabled"
adb shell 'echo "chrome --no-default-browser-check --no-first-run
--disable-fre" > /data/local/chrome-command-line'
adb shell am start -n
com.android.chrome/com.google.android.apps.chrome.Main -d "$URL"
after running the emulator with "emulator ... -selinux disabled"
Hope this helps someone else trying to do this!
Well great news. I don't know what did it but the welcome screen has gone
away using Galaxy Nexus 6 with nothing else changed. Maybe the
"chromeOptions" in protractor are incompatible with 6+. Thanks for the help
guys.
I downgraded my AVD to Marshmellow (6.0) and I got an interesting line
that I wasn't getting with 7.0. Additionally it looks like 7.0 is extremely
hard to get root access on.
[100%]
/data/local/tmp/com.android.chrome_53.0.2785.124-278512411_minAPI21x86nodpi_apkmirror.com.apk
/data/local/tmp/com.android.chrome_53.0.2785.124-278512411_minAPI21x86nodpi_apkmirror.com.apk
Is the message I got from I added chrome to my Galaxy Nexus with Android
6.0.
However the adb shell commands did not work.
How do I check which one I am supposed to be using? I tried all three.
Hmm are you running Content Shell or Android WebView?
If not, you want to use instead (or in addition) -
/data/local/tmp/chrome-command-line
/data/local/chrome-command-line
See
https://cs.chromium.org/chromium/src/build/android/adb_chrome_public_command_line?q=adb_chrome_public_command_line&sq=package:chromium&dr=C&l=21
.
☆*PhistucK*
<https://lh3.googleusercontent.com/-xnGu12vdA88/WAYdrO5wcmI/AAAAAAAAAGU/l7G0jZSEsPE2vHVmbgGl0PNXKedGf6VOgCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.02.20%2BAM.png>
Looks like it was already running as root... the mystery deepens.
<https://lh3.googleusercontent.com/-Sl5PJeGz5QA/WAYfRsrfEKI/AAAAAAAAAGY/z50N9PLs_0Yz9wjtH2-Fjx6rpPoh8h9gQCLcB/s1600/Screen%2BShot%2B2016-10-18%2Bat%2B10.09.41%2BAM.png>
Can't seem to make it work :(
I'm trying to run some automated tests and the "Welcome to Chrome" pop up
is being rather troublesome. I've attempted to add flags to skip it with
adb shell --no-first-run and --disable-fre but neither of the flags
actually got set.
My env is OS X running protractor with appium and an Android emulator. The
tests run fine but I am finding myself unable to do anything but manually
click the welcome modal. I've used at least one to two pages of suggestions
on 10 hours of semi-creative googling. I'm hoping most answers are just
outdated.
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/b7886020-fb3a-4876-8fbe-ebe53b25d752%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/b7886020-fb3a-4876-8fbe-ebe53b25d752%40chromium.org?utm_medium=email&utm_source=footer>
.

[Baurzhan]

String context = driver.getContext(); // = "CHROMIUM"
driver.context("NATIVE_APP");
driver.findElement(By.id("com.android.chrome:id/terms_accept")).click();
driver.findElement(By.id("com.android.chrome:id/negative_button")).click();
driver.context(context);

Post by Eric Savoie
I'm trying to run some automated tests and the "Welcome to Chrome" pop up
is being rather troublesome. I've attempted to add flags to skip it with
adb shell --no-first-run and --disable-fre but neither of the flags
actually got set.
My env is OS X running protractor with appium and an Android emulator. The
tests run fine but I am finding myself unable to do anything but manually
click the welcome modal. I've used at least one to two pages of suggestions
on 10 hours of semi-creative googling. I'm hoping most answers are just
outdated.

[Bill Hileman]

I realize this is an old post, but your code helped me get over a hump.

The only thing I added to my version was to avoid any error if the alerts
were not present by checking for their existence first:

String context = driver.getContext(); // = "CHROMIUM"
driver.context("NATIVE_APP");
if
(!driver.findElements(By.id("com.android.chrome:id/terms_accept")).isEmpty())
{
driver.findElement(By.id("com.android.chrome:id/terms_accept")).click();
if
(!driver.findElements(By.id("com.android.chrome:id/negative_button")).isEmpty())

driver.findElement(By.id("com.android.chrome:id/negative_button")).click();
}
driver.context(context);

Post by Baurzhan
String context = driver.getContext(); // = "CHROMIUM"
driver.context("NATIVE_APP");
driver.findElement(By.id("com.android.chrome:id/terms_accept")).click();
driver.findElement(By.id("com.android.chrome:id/negative_button")).click();
driver.context(context);

Post by Eric Savoie
I'm trying to run some automated tests and the "Welcome to Chrome" pop up
is being rather troublesome. I've attempted to add flags to skip it with
adb shell --no-first-run and --disable-fre but neither of the flags
actually got set.
My env is OS X running protractor with appium and an Android emulator.
The tests run fine but I am finding myself unable to do anything but
manually click the welcome modal. I've used at least one to two pages of
suggestions on 10 hours of semi-creative googling. I'm hoping most answers
are just outdated.