Currently, one service is allowed to have multiple psp during ADDPSP. Notice there is comment mentioned that it's a feature to allow single service has multiple psp in different push service type. Unfortunately, sometimes a user might add a service psp in same push service type, since there is no warning message for that, under this situation, no one even know there are multiple service<->psp pair in same push service type, and only the very first one returned in getting service will be working in runtime. That will cause trouble in subscribe and push operation. It results in some issues and hard to discover the root cause. So introducing this fix to prevent a user to add redundant service<->psp in same push service type.
One method AddPushServiceProviderToService(...) in pushdb.go is updated to fix this issue. And psp in different push service type is still allowed to add under the same service.
Currently, one service is allowed to have multiple psp during ADDPSP. Notice there is comment mentioned that it's a feature to allow single service has multiple psp in different push service type. Unfortunately, sometimes a user might add a service psp in same push service type, since there is no warning message for that, under this situation, no one even know there are multiple service<->psp pair in same push service type, and only the very first one returned in getting service will be working in runtime. That will cause trouble in subscribe and push operation. It results in some issues and hard to discover the root cause. So introducing this fix to prevent a user to add redundant service<->psp in same push service type.
One method AddPushServiceProviderToService(...) in pushdb.go is updated to fix this issue. And psp in different push service type is still allowed to add under the same service.