Can't support longest routing table prefix match

ZeroTier does not support the longest prefix match. Here are my routing settings: 172.28.0.0/16 (lan), 192.168.1.0/24 via 172.28.0.1, 192.168.1.99/32 via 172.28.0.99. The versions of both the Linux client and the Android client are 1.14.x. When accessing the Linux from the Android, for the routing rule of 192.168.1.99/32 via 172.28.0.99, it can work properly all the time only after deleting the rule 192.168.1.0/24 via 172.28.0.1. If the rule 192.168.1.0/24 via 172.28.0.99 is added, it will intermittently fail, sometimes working and sometimes not. I’d like to ask if ZeroTier does not support the longest prefix match or if there is a bug?