Note that with this release the minimum recommended Firefox version
has changed to Firefox ≥60.
macOS 10.15 (Catalina):
Due to the recent requirement from Apple that all programs must
be notarized, geckodriver will not work on Catalina if you manually
download it through another notarized program, such as Firefox.
Whilst we are working on a repackaging fix for this problem, you
can find more details on how to work around this issue in the
macOS notarization section of the documentation.
You must still have the Microsoft Visual Studio redistributable
runtime installed on your system for the binary to run. This
is a known bug which we weren't able fix for this release.
Marionette will only be enabled in GeckoView based applications when the
devtools.debugger.remote-enabledis set to
moz:firefoxOptions. This will be fixed in the Firefox 90 release for Android.
In some cases geckodriver could crash due to a stack overflow when handling
certain device errors.
Support for Firefox on Android
Starting with this release geckodriver is able to connect to
Firefox on Android systems, and to control packages based on
Support for Android works by the geckodriver process running on
a host system and Firefox running within either an emulator or
on a physical device connected to the host system. This requires
you to first enable remote debugging on the Android device.
The full list of new capabilities specific to Android, instructions
how to use them, and examples can be found in the
documentation on MDN.
When the session is created, the
android" instead of reporting the platform of the host
Continued Marionette refactoring changes
0.25.0 came with a series of internal changes for how geckodriver
communicates with Firefox over the Marionette protocol. This
release contains the second half of the refactoring work.
Connection attempts to Firefox made more reliable
geckodriver now waits for the Marionette handshake before assuming
the session has been established. This should improve reliability
in creating new WebDriver sessions.
Corrected error codes used during session creation
When a new session was being configured with invalid input data,
the error codes returned was not always consistent. Attempting
to start a session with a malformed capabilities configuration
will now return the invalid argument error consistently.