Reqwest 0.12.16 fails to compile on OSX

[LarryOsterman]

Our CI pipeline just started failing with the following error when picking up Reqwest 0.12.16. 0.12.15 seems to have worked.

The reqwest options in our cargo.toml file are:

reqwest = { version = "0.12", features = [
  "json",
  "stream",
], default-features = false }

2025-05-27T21:20:05.4053480Z    --> /Users/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/reqwest-0.12.16/src/async_impl/client.rs:598:53
2025-05-27T21:20:05.5061060Z     |
2025-05-27T21:20:05.6067880Z 598 |                 TlsBackend::BuiltNativeTls(conn) => ConnectorBuilder::from_built_default_tls(
2025-05-27T21:20:05.7074520Z     |                                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-05-27T21:20:05.8078660Z ...
2025-05-27T21:20:05.9082620Z 606 |                     config.nodelay,
2025-05-27T21:20:06.0084760Z     |                     -------------- argument #6 of type `std::option::Option<&str>` is missing
2025-05-27T21:20:06.1087760Z     |
2025-05-27T21:20:06.2092520Z note: associated function defined here
2025-05-27T21:20:06.3097060Z    --> /Users/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/reqwest-0.12.16/src/connect.rs:254:19
2025-05-27T21:20:06.4106580Z     |
2025-05-27T21:20:06.5108980Z 254 |       pub(crate) fn from_built_default_tls<T>(
2025-05-27T21:20:06.5462930Z     |                     ^^^^^^^^^^^^^^^^^^^^^^
2025-05-27T21:20:06.6463970Z ...
2025-05-27T21:20:06.7466070Z 260 | /         #[cfg(any(
2025-05-27T21:20:06.8466790Z 261 | |             target_os = "android",
2025-05-27T21:20:06.9469010Z 262 | |             target_os = "fuchsia",
2025-05-27T21:20:07.0470220Z 263 | |             target_os = "illumos",
2025-05-27T21:20:07.1472000Z ...   |
2025-05-27T21:20:07.2472990Z 271 | |         ))]
2025-05-27T21:20:07.3475030Z 272 | |         interface: Option<&str>,
2025-05-27T21:20:07.4476260Z     | |_______________________________-
2025-05-27T21:20:07.5478070Z help: provide the argument
2025-05-27T21:20:07.6480570Z     |
2025-05-27T21:20:07.7482070Z 598 -                 TlsBackend::BuiltNativeTls(conn) => ConnectorBuilder::from_built_default_tls(
2025-05-27T21:20:07.8516420Z 599 -                     http,
2025-05-27T21:20:07.9517080Z 600 -                     conn,
2025-05-27T21:20:08.0519070Z 601 -                     proxies.clone(),
2025-05-27T21:20:08.1520000Z 602 -                     user_agent(&config.headers),
2025-05-27T21:20:08.2522040Z 603 -                     config.local_address,
2025-05-27T21:20:08.3523530Z 604 -                     #[cfg(any(target_os = "android", target_os = "fuchsia", target_os = "linux"))]
2025-05-27T21:20:08.4525820Z 605 -                     config.interface.as_deref(),
2025-05-27T21:20:08.5528210Z 606 -                     config.nodelay,
2025-05-27T21:20:08.6531180Z 607 -                     config.tls_info,
2025-05-27T21:20:08.7533230Z 608 -                 ),
2025-05-27T21:20:08.8536170Z 598 +                 TlsBackend::BuiltNativeTls(conn) => ConnectorBuilder::from_built_default_tls(http, conn, proxies.clone(), user_agent(&config.headers), config.local_address, /* std::option::Option<&str> */, config.tls_info, config.nodelay),
2025-05-27T21:20:08.9537760Z     |
2025-05-27T21:20:09.0539480Z 

[seanmonstar]

Hm, do we have a hole in our CI? Do you happen to know the fix?

[yhx-12243]

Reproducible on my macOS, too.

[yhx-12243]

The fix seems easy, since it produces the inconsistency of attribute of interface due to 114d97c. (the error message just gives the solution).

[seanmonstar]

Sorry about that, v0.12.17 is out now.

[Xuanwo]

Sorry about that, v0.12.17 is out now.

How about yanking 0.12.16 to avoid it been used?

[seanmonstar]

I don't see a need to yank, if someone upgraded and it didn't fail to compile, they're fine.

[zerosnacks]

Related: #2699 on 0.12.16 + 0.12.17

[LarryOsterman]

Hm, do we have a hole in our CI? Do you happen to know the fix?

Sorry about taking so long to get back on this - I unfortunately don't have a mac or OSX machine to investigate further, however the attached fixes above are the ones I would have suggested for this issue.