Some background: for the last couple of months, we've been successfully using Azure Functions v4 with .NET isolation and .NET 6 for our back-end functions to be called by PlayFab via ExecuteFunction calls.
However, upgrading the PlayFabAllSDK NuGet from 1.108.220118 to any later version (e.g. the next 1.127.220718, or the latest 1.133.220816) seems to break the local debugging functionality.
After upgrading the NuGet package all ExecuteFunction calls issued will directly go to PlayFab instead of the API running locally, bypassing the fact that there’s a "playfab.local.settings.json" file in the working directory containing an API redirection, as described in the documentation:
{ "LocalApiServer": "http://localhost:7071/api/" }
Note: although too general for our use, putting the "playfab.local.settings.json" file in "%Temp%" doesn't work anymore neither after the upgrade, as it does before.
This has been working fine for the past couple of months. Upgrading the NuGet package to the next version 1.127.220718 breaks the local debugging functionality. Downgrading back to 1.108.220118 restores working condition.
The documentation mentions no changes in how to allow local debugging. Has this been changed nonetheless or is this a bug?