pre-release version 1.8.36 (beta) has an issue with routing outbound traffic

[amircybersec]

在提出问题前请先自行排除服务器端问题，同时也请通过搜索确认是否有人提出过相同问题。

预期行为

描述你认为应该发生什么

The app should connect to server and pass data through the server. In the pre-release version it connected but no traffic flows through the app.

实际行为

描述实际发生了什么

It seems like pre-release version 1.8.36 (beta) has an issue with routing outbound traffic. The app connects to a server and passes the HTTP test BUT no traffic flows through the app. I tested the release version of the app 1.8.35 and it works well with the same server config.

I tested this on Android.

复现方法

1. Try connecting to a given shadowsocks or vless proxy server
2. visit a website

日志信息

通过adb logcat -s com.v2ray.ang GoLog V2rayConfigUtilGoLog Main获取日志。请自行删减日志中可能出现的敏感信息。

如果问题可重现，建议先执行adb logcat -c清空系统日志再执行上述命令，再操作重现问题。

在这里粘贴日志

环境信息

额外信息（可选）

[2dust]

Since developers don't have that much time to reproduce the problem, please export the full configuration and point out the part that is problematic

[amircybersec]

The problem is not the configuration. It is plain shadowsocks.

{
  "dns": {
    "hosts": {
      "geosite:category-porn": "127.0.0.1",
      "domain:googleapis.cn": "googleapis.com"
    },
    "servers": [
      "1.1.1.1"
    ]
  },
  "inbounds": [
    {
      "listen": "127.0.0.1",
      "port": 10808,
      "protocol": "socks",
      "settings": {
        "auth": "noauth",
        "udp": true,
        "userLevel": 8
      },
      "sniffing": {
        "destOverride": [
          "http",
          "tls"
        ],
        "enabled": true
      },
      "tag": "socks"
    },
    {
      "listen": "127.0.0.1",
      "port": 10809,
      "protocol": "http",
      "settings": {
        "userLevel": 8
      },
      "tag": "http"
    }
  ],
  "log": {
    "loglevel": "warning"
  },
  "outbounds": [
    {
      "mux": {
        "concurrency": -1,
        "enabled": false,
        "xudpConcurrency": 8,
        "xudpProxyUDP443": ""
      },
      "protocol": "shadowsocks",
      "settings": {
        "servers": [
          {
            "address": "23.93.87.111",
            "level": 8,
            "method": "2022-blake3-aes-256-gcm",
            "ota": false,
            "password": "REMOVED_xlbddCxxQRu9U5bSs8sXXl9zXgssjwN+2MO4=:q/aplcNUxxxxxlGhLF3NQ77JIogalyq8Z5j7p09hgO0=",
            "port": 29121
          }
        ]
      },
      "streamSettings": {
        "network": "tcp",
        "security": ""
      },
      "tag": "proxy"
    },
    {
      "protocol": "freedom",
      "settings": {},
      "tag": "direct"
    },
    {
      "protocol": "blackhole",
      "settings": {
        "response": {
          "type": "http"
        }
      },
      "tag": "block"
    }
  ],
  "remarks": "m04uonks9",
  "routing": {
    "domainStrategy": "IPIfNonMatch",
    "rules": [
      {
        "ip": [
          "1.1.1.1"
        ],
        "outboundTag": "proxy",
        "port": "53",
        "type": "field"
      },
      {
        "domain": [
          "domain:ir",
          "geosite:category-ir",
          "geosite:private"
        ],
        "outboundTag": "direct",
        "type": "field"
      },
      {
        "ip": [
          "geoip:ir",
          "geoip:private"
        ],
        "outboundTag": "direct",
        "type": "field"
      },
      {
        "domain": [
          "geosite:category-porn"
        ],
        "outboundTag": "block",
        "type": "field"
      },
      {
        "ip": [
          "10.10.34.34",
          "10.10.34.35",
          "10.10.34.36"
        ],
        "outboundTag": "block",
        "type": "field"
      }
    ]
  }
}

I have altered the IP address and the key in the config.

When I use the same config with version 1.8.35 (official release), it works well. I tested with MahsaNG app v8.0 that uses Xray core version v1.18.13, Lib v26, it works well tool. I am going to capture logcat and report back.

I suggest to hold off with the release of beta until we resolve this issue since it can break things for a lot of folks.