io.seata.config.FileConfiguration : Could not found property service.vgroup_mapping.null, try to use default value instead

In application.properties:
spring.cloud.alibaba.seata.tx-service-group=my_test_tx_group

In resource/file.conf:
service {
#vgroup->rgroup
vgroup_mapping.my_test_tx_group = "default"
#vgroupMapping.my_test_tx_group = "default"
#only support single node
default.grouplist = "127.0.0.1:8091"
#degrade current not support
enableDegrade = false
#disable
disable = false
#unit ms,s,m,h,d represents milliseconds, seconds, minutes, hours, days, default permanent
max.commit.retry.timeout = "-1"
max.rollback.retry.timeout = "-1"
disableGlobalTransaction = false
}
seata-server
In file.conf:
service {
#transaction service group mapping
vgroup_mapping.my_test_tx_group = "default"
#only support when registry.type=file, please don't set multiple addresses
default.grouplist = "127.0.0.1:8091"
#disable seata
disableGlobalTransaction = false
}

WARN 192 --- [nfigOperate_2_2] io.seata.config.FileConfiguration : Could not found property service.vgroup_mapping.null, try to use default value instead.
2020-03-23 02:43:20.417 WARN 192 --- [nfigOperate_2_2] io.seata.config.FileConfiguration : Could not found property service.vgroup_mapping.null, try to use default value instead.
2020-03-23 02:43:20.417 ERROR 192 --- [ main] i.s.c.r.netty.NettyClientChannelManager : no available service 'null' found, please make sure registry config correct

Compare the transaction group setting in application.properties with the service.vgroup_mapping entries in resource/file.conf and file.conf, then trace how the client reads these settings during startup. Reproduce the configuration and verify that the service lookup no longer uses a null group and can find 127.0.0.1:8091.

Written by the indexing model from the issue text.