[1.12.0-alpha.2] Android inbound/tun[0]: configure tun interface: invalid argument

[douniwan5788]

Operating system

Android

System version

13

Installation type

sing-box for Android Graphical Client

If you are using a graphical client, please provide the version of the client.

No response

Version

Description

start inbound/tun[0]: configure tun interface: invalid argument

Reproduction

{
    "tag": "tun-in",
    "type": "tun"
}

Logs

Supporter

• I am a sponsor

Integrity requirements

• I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
• I confirm that I have provided the server and client configuration files and process that can be reproduced locally, instead of a complicated client configuration file that has been stripped of sensitive data.
• I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported, instead of depending on remote servers, TUN, graphical interface clients, or other closed-source software.
• I confirm that I have provided the complete configuration files and logs, rather than just providing parts I think are useful out of confidence in my own intelligence.

[bubulgum]

same issue Android 14, samsung s23, s24

[nekohasekai]

Can you provide a simple but complete configuration that reproduces the problem?

[bubulgum]

updated from Google Store to last version. can't run any servers. screens attached

[douniwan5788]

@nekohasekai

{
    "log": {
        "disabled": false,
        "level": "trace",
        "timestamp": true
    },
    "dns": {
        "servers": [
            {
                "tag": "local_https_dns",
                "type": "https",
                // "server": "1.1.1.1",
                "server": "one.one.one.one",
                "domain_resolver": "local_dns"
                // "detour": "direct-out"
            },
            {
                "tag": "local_dns",
                "type": "local"
                // "type": "dhcp",
            }
        ]
    },
    "inbounds": [
        {
            "tag": "tun-in",
            "type": "tun",
            "address": [
                "172.19.0.1/30",
                "fdfe:dcba:9876::1/126"
            ]
        }
    ],
    "outbounds": [
        {
            "tag": "direct-out",
            "type": "direct"
        }
    ]
}

Strangely, the error switches to FATAL[0000] create service: initialize inbound[0]: domain resolver not found: local_dns when detour is not specified, and to FATAL[0000] create service: initialize inbound[0]: missing address resolver for server: one.one.one.one when "detour": "direct-out" is set.