1751278 - Using the "--profile" argument in "moz:firefoxOptions['args']" generates two profile entries in the geckoview config file

Status: NEW

(Testing :: geckodriver, defect, P3)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Specifying a Firefox profile via moz:firefoxOptions["args"] causes the geckoview config file on the Android device to contain two entries for--profile` like:

1642709641495	geckodriver::android	DEBUG	Content of generated GeckoView config file:
## GeckoView configuration YAML
##
## Auto-generated by geckodriver.
## See https://mozilla.github.io/geckoview/consumer/docs/automation.
---
env:
  MOZ_CRASHREPORTER: "1"
  MOZ_CRASHREPORTER_NO_REPORT: "1"
  MOZ_CRASHREPORTER_SHUTDOWN: "1"
args:
  - "--marionette"
  - "--remote-debugging-port"
  - "--profile"
  - /sdcard/Android/data/org.mozilla.geckoview.test_runner/files/test_root/org.mozilla.geckoview.test_runner-geckodriver-profile
  - "--profile"
  - /Users/henrik/code/gecko/_test-profile/

Note that the first entry is what we want. But the second entry is the source profile from the host.

This is a regression in geckodriver 0.30.0.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

This is a regression from bug 1721447 since we use the application arguments from moz:firefoxOptions to start Firefox on Android.

To fix this we will have to ignore the --profile argument and the immediate successor.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1721447

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

It's not a blocking issue and the GeckoView application is only considering the first profile as passed in. So it's not a regression we have to immediately work on. If time permits we could still try to get it into the 0.31.0 release.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

We should be safe to let this slip to the next 0.32.0 release.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+1]]

There was no time for the 0.32.0 release. Lets keep it on the radar for 0.33.0.