Help with function implementation

[ElisMia]

hey! Could somebody help? For me functions for the assistant are not working anymore, maybe I'm missing something not sure. they were working before, but then after this new update of Open ai (v2, the upde of open ai, not if ths package), they stopped working (at least I think it's related to this, because coe from my side didn't change, but functions stopped working. also image generation func is not working anymore, but was working before).

I was trying to debug and find a reason why, but still don't understand. It seems like the function definition is fine and I pass it to the assistant, and I see that the assistant tries to call the function. (I tested it in Playground and the assistant calls it, as well as it call it in Unity) but the function in Unity that needs to be called from assistant in Unity is not called, and the assistant says something like "Sorry, I don't have access to the function right now". I see when I debug that it's calling function (the task said in assiatnt function is fulfilled and assistant fill out parameters of function), and output awaited for it. but it gives me always the error "Failed to find valid function" and Unity function itself not called. I was trying different definitions of functions and debug, but no clue what's the issue, or if APi is not working anymore in general. right now I use this tool implementation:
Tool sapServiceTool = Tool.GetOrCreateTool(typeof(SAPService), nameof(SAPService.CallSAPServiceAsync));

SAPService is implemented in similar way to Weather example, as I suppose this is the way to go, notsure if just reguar declaration would work...

and here is how I get tools outpult:

if (run.RequiredAction != null)
{
    var toolOutputs = await assistant.GetToolOutputsAsync(run.RequiredAction.SubmitToolOutputs.ToolCalls);

    foreach (var toolOutput in toolOutputs)
    {
        Debug.Log($"tool call output: {toolOutput.Output}");
    }
               
    // submit the tool outputs
    run = await run.SubmitToolOutputsAsync(toolOutputs);
    // waiting while run in Queued and InProgress
    run = await run.WaitForStatusChangeAsync();
}

I was reading some of the discussions, but still not really sure what's missig... maybe somebody can help, or has an working example how does this custom function need to be used, to call function in unity.

and here is error I get:

[StephenHodgson]

are you making sure to reference your tool when you create your assistant?

[ElisMia]

okay, I checked the assiatnt itself, and asssitant has in list this tool, but if I check this 2 functions:

Tools.IsToolRegistered(tool); -it gives false. then it's not registered

and also I don't see the function in the list of tools there: Tool.GetAllAvailableTools(). there is only old implementation of function and no new one for some reason

[StephenHodgson]

Sounds like your tool is somehow getting unregistered between setting it and when you try to invoke it.

You can attempt to register the tool if it isn't already registered:

Tool.TryRegisterTool(tool);

if (run.RequiredAction != null)
{
    var toolOutputs = await assistant.GetToolOutputsAsync(run.RequiredAction.SubmitToolOutputs.ToolCalls);

    foreach (var toolOutput in toolOutputs)
    {
        Debug.Log($"tool call output: {toolOutput.Output}");
    }
               
    // submit the tool outputs
    run = await run.SubmitToolOutputsAsync(toolOutputs);
    // waiting while run in Queued and InProgress
    run = await run.WaitForStatusChangeAsync();
}

[ElisMia]

I added it, now the tool is registered and i see it in the list, but still I get exception when it tries to call the tool for assistant automatically.

and also some functions for some reson it's not possible to register, it throughs error, that this is not a function (and then don't register it), even if it has info that it's function. but it's maybe different topic

[ElisMia]

thank you. I made manuall invocation and submitting tool result. it works with manual way. seems to be some problem with automatic invocation

[StephenHodgson]

Ok, thanks for the heads up.
I'll double check the behavior before next release.