Because the ResourceProviderService wasn't marked as a singleton in the aspnet layer it was being recreated fresh for each grpc request, each fresh creation was then freshly creating the users Provider object and so losing any instance state they had set on it.
This also fixed some NPEs in the marshaling layer in the case where Struct fields were null.
Reported on community slack.
Because the
ResourceProviderServicewasn't marked as a singleton in the aspnet layer it was being recreated fresh for each grpc request, each fresh creation was then freshly creating the usersProviderobject and so losing any instance state they had set on it.This also fixed some NPEs in the marshaling layer in the case where
Structfields were null.