[Bug] Tailscale Android beta app doesn't create routes when using Headscale

[Ziomal12]

Is this a support request?

• This is not a support request

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When connected to self-hosted Headscale instance android client cannot ping nor initiate connections to other devices on tailnet. (Checked with Termux ping command, Ping tools and CX file explorer for SMB and ConnectBot for SSH).

The only scenario I was able to get a ping was when pinging exit node that the android client was currently using.

Other devices in tailnet can ping android client without issues all the time.

Seems like when connected to Headscale server the app doesn't create routes:
headscale:
Routes: [ 100.100.100.100/32 -> 0.0.0.0 tun0 mtu 0 ]
tailscale:
Routes: [ 100.76.31.70/32 -> 0.0.0.0 tun0 mtu 0,100.87.172.75/32 -> 0.0.0.0 tun0 mtu 0,100.91.28.81/32 -> 0.0.0.0 tun0 mtu 0,100.119.22.118/32 -> 0.0.0.0 tun0 mtu 0,fd7a:115c:a1e0::/48 -> :: tun0 mtu 0,100.100.100.100/32 -> 0.0.0.0 tun0 mtu 0 ]

Bug filed with Tailscale tailscale/tailscale#11731

Expected Behavior

It should connect

Steps To Reproduce

1. Download Android Beta Client from Play Store.
2. Login to self hosted tailscale instance.
3. Enable tailscale.
4. Try to ping other device in tailnet from Android client (fails).
5. Enable exit node.
6. Try to ping currently used exit node from android client (successful).

Environment

- OS: Ubuntu 22 LTS
- Headscale version: 0.23.0-Beta9
- Tailscale version: 1.65.40-t449be38e0-g24dc71d8d24
Docker and native Headscale version 

Runtime environment

• Headscale is behind a (reverse) proxy
• Headscale runs in a container

Anything else?

No response

[Ziomal12]

Fixed by Tailscale app update.