Seata1.3 nacos1.3.1 springboot 2.2.1 seata 服务端和客户端都注册在public空间时才能成功

Seata1.3 nacos1.3.1 springboot 2.2.1 seata 服务端和客户端都注册在public空间时才能成功
如果把 public 配置克隆 自定义 namespace 并 把 seata 服务端 客户端都切换到自定义 namespace
客户端就无法注册到 seata的服务端
持续报错 no available service 'default' found, please make sure registry config correct

请问 1.3是只能在 public 空间下使用吗?

Reproduce the reported setup with Seata 1.3, Nacos 1.3.1, and Spring Boot 2.2.1, switching both client and server from public to a cloned custom namespace. Start with the registry configuration and the “no available service 'default' found” error; done means custom-namespace registration works or the limitation is clearly documented.

Written by the indexing model from the issue text.