So we've added a new secret key to use on our build environment, but afterwards any time I switch environments in the PlayFab extension in Unity it always grabs that one instead of the default.
This is really not security conscious as the whole point of making multiple secret keys is to control access, but as it works now everyone ends up using the same key!
PlayFabEdEx gets the first active Secret Key by default and writes it to PlayFabSharedSettings. If you don't need it to get it automatically, you can comment out the corresponding code and configure it manually in PlayFabSharedSettngs, refer to Installing the PlayFab SDK for Unity - PlayFab | Microsoft Docs. To clarify, PlayFabEdEx is designed to help configure PlayFabSDK, if it affects your development, you can remove it.
Also, you can set it manually in code via PlayFabSettings.DeveloperSecretKey=" ".
12 People are following this question.
