I get the same bug as in the post above.
When I call unlockContainerInstance, the call succeeds at the same time as the call fails, and the call succeeds again, then the call fails. In the order of error, success, success, and error, there are 4 times, and the contents of the same container are received twice.
It seems like a very fast unlockcontainer call produces multiple results.
It has been confirmed that one container item (by count 1) is unlocked up to 3 times.
It's like a huge bug.
As it is discussed previously, this should be fixed in the upcoming new commerce system (Though the ETA is still unknown). please continue to keep track of the update news.
Thus, the issue can be avoided by workarounds. For example, you may deny the corresponding client APIs via editing API access policy and handle the unlock process on Cloud Script/Azure Function via server API. While you may also store a last-unlock timestamp in Player Internal Data, which will be checked at the beginning of the process, to ensure a fixed time interval.
3 People are following this question.
