I'm not sure if this is a bug in PlayFab or if I'm doing something wrong:
I'm using consumable containers with "By Count"=1 to act as reward chests. In testing, there was a bug in our client that called PlayFabClientAPI.UnlockContainerInstance two times in fairly rapid succession targeting the same ContainerItemInstanceId. I expected PlayFab to reject the 2nd call because the instance was already unlocked, but I found 2 copies of the container's item in my inventory.
Is it the client's job to defend against this? Am I misunderstanding how consumable-by-count works?