[🚀 Feature]: Error when Selenium Manager used on unsupported architecture

[titusfortner]

Feature and motivation

Right now, Selenium Manager is called when a driver isn't specified or found on PATH. We only support 3 architectures, though. We should add code to explicitly check the user's architecture in preparation for additional additional architectures and throw an error until the architecture is actually supported.

This isn't as much of a problem while the Manager is in a "fall back" mode, but it can cause unexpected/confusing errors especially once we stop hiding them.

[titusfortner]

Turns out that Mac ARM architecture works just fine with AMD Selenium Manager, so that one isn't an issue.

So, I'm going off of this list here: #11357

There are drivers available in various places for each of these architectures, but our current selenium manager binaries won't even run on them:
linux-32
win32
linux-arm64
win-arm64
linux-armv7

If we checked in a 32 bit version of Selenium Manager for Windows & Linux, it should also work for 64 bit OS, right?

[titusfortner]

Here are some rough numbers for geckodriver downloads:

Architecture	Percent	Currently Supported
linux64	51%	✔
win64	24%	✔
macos	9%	✔
macos-aarch64	5%	✔
win32	5%
win-aarch64	2%
linux-aarch64	2%
linux32	1%

So presumably we are currently supporting "only" ~90% of usage

[bonigarcia]

To clarify these figures a bit, the Selenium Manager Rust code already supports every platform in geckodriver (including win32, linux32, etc.). But it is true that the current compilation is only for win64, linux64, and mac64. So win32 and linux32 cannot be downloaded with Selenium Manager since the binary cannot be executed. But I have doubts ARM64 in Windows and Linux. Maybe the x64 binary can be executed in Windows and Linux (like in macOS). In that case, the win-aarch64 and linux-aarch64 are also supported. Unfortunately, I don't have an ARM64 machine for Windows or Linux to check it.

[titusfortner]

I'm almost certain arm64 will need to be supported separately for Linux/Windows.

So specifically for next release we need to add to the bindings checks with errors for the 4 above that can't be obtained automatically via Selenium right now.

I'm *hoping we might be able to build & bundle 32 bit versions of Linux/Windows and that they will still work for 64 bit Linux/Windows. That would get us to > 95% at least, which is good enough until we figure out cross compilation.