IPv6 priority in Windows and Apple issues

Hi,

Version: 3.6.0 binary for Windows 11 and Apple (Mac OS, iOS)
Configuration 1:
remote <my_vpn>
remote <my_vpn> 443 tcp

Expected behavior: On a dual stack environment, connection to <my_vpn> via udp6, if the connection times out, then tcp6 should be tried. In a IPv4 only (for example Mobile) or failed IPv6 connection attempt it should use udp4. If those attempts fail, tcp4 should be the last resort.

Seen behavior:
Windows 11 on dual stack environment connects via udp4 to the server. In an IPv6 only, it connects via tcp6, it never tries to use udp6.
Mac Book on dual stack environment connects via udp4 (as Windows platform.). In an IPv4 only, connection fails with
"Endpoint address failmy (IPv6) is incompatible with transport protocol (udp4)"

Configuration 2:
remote <my_vpn> 1194 udp6
remote <my_vpn>
remote <my_vpn> 443 tcp

Expected behavior: As above.

Seen behavior:
Windows 11 on dual stack environment: Connection works as expected.
MacBook on dual stack environment works as expected, but in an IPv4 only environment, connection cannot be established and the error is
"Endpoint address family (IPv4) is incompatible with transport protokol (udp6)"

Did anyone noticed this behavior? As I do not have the infrastructure to compile the newest commit to test if it is already solved, I would appreciate your help.

BR

No source files, tests, or entry points are identified in the issue. Start by reproducing the listed remote configurations on the affected Windows and Apple environments, then trace address-family and transport fallback handling. Done means IPv6 and IPv4 environments follow the documented UDP-then-TCP fallback order without incompatible-address errors.