Tor 0.3.2 rejects connections to raw ipv6 addresses

OS X 10.11.6, Tor Browser 7.5

I have to configure TB to use a socks5 proxy to reach the internet (I predict this is unrelated). I disabled safe logging.

Attempting to go to https://[2a00:1450:401b:800::200e]/ (google) produces the following Tor logs.

1/26/18, 14:51:25.600 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop 
1/26/18, 14:51:48.700 [NOTICE] Bootstrapped 90%: Establishing a Tor circuit 
1/26/18, 14:51:50.000 [NOTICE] Tor has successfully opened a circuit. Looks like client functionality is working. 
1/26/18, 14:51:50.000 [NOTICE] Bootstrapped 100%: Done 
1/26/18, 14:51:50.900 [NOTICE] New control connection opened from 127.0.0.1. 
1/26/18, 14:51:51.000 [NOTICE] New control connection opened from 127.0.0.1. 
1/26/18, 14:54:06.900 [WARN] Your application (using socks5 to port 443) gave Tor a malformed hostname: "2a00:1450:401b:800::200e". Rejecting the connection. 
1/26/18, 14:54:06.900 [WARN] Your application (using socks5 to port 443) gave Tor a malformed hostname: "2a00:1450:401b:800::200e". Rejecting the connection. 
1/26/18, 14:55:38.200 [WARN] Your application (using socks5 to port 443) gave Tor a malformed hostname: "2a00:1450:401b:800::200e". Rejecting the connection. 
1/26/18, 14:55:38.200 [WARN] Your application (using socks5 to port 443) gave Tor a malformed hostname: "2a00:1450:401b:800::200e". Rejecting the connection. 

https://ipv6.google.com works with every 6th circuit. I'm sure this is unrelated and has to do with exits half supporing ipv6 or something.