Looks like there's a disparity between PlayFabCloudScriptInstanceAPI and PlayFabCloudScriptAPI in UnitySDK-2.183.231124
PlayFabCloudScriptInstanceAPI.ExecuteFunction does not support local debugging for Azure functions using PlayFabSettings.LocalApiServer.
I can confirm that copying and pasting the code from PlayFabCloudScriptAPI.ExecuteFunction into PlayFabCloudScriptInstanceAPI.ExecuteFunction, and passing 'this' into PlayFabHttp.MakeApiCallWithFullUri, works fine.
Could you please tell me if you receive any error message when try to local debug PlayFabCloudScriptInstanceAPI.ExecuteFunction? Did this cause any impact?
No errors, it just tries to use the live version of the Azure function. The code that fetches the PlayFabSettings.LocalApiServer is missing entirely from PlayFabCloudScriptInstanceAPI.ExecuteFunction.
Can you use the static API instead of the instance API? Is there any concern on using the static API to test Azure function locally?
You can use the instance API in your system as you want. But currently the local test Azure Function is design for static APIs, you can do the modification to the SDK to make instance API work with local Azure Function test environment. Thank you for sharing that.
2 People are following this question.
