Creating Unchase OData V1-V4 Connected Service (Unauthorized)

[unchase]

Creating Unchase OData V1-V4 Connected Service (Unauthorized)

[gem81]

as a result, functions are not created.

[unchase]

Before code generation, did you check options "Use network credentials for connecting to the endpoint :" and/or "Use web-proxy for connecting to the endpoint :" along with "Use web-proxy credentials for connecting to the endpoint :"?
What generation method did you use: "Inner" or "SimpleOData"?

What endpoint did you use?

[gem81]

Before code generation, did you check options "Use network credentials for connecting to the endpoint :" and/or "Use web-proxy for connecting to the endpoint :" along with "Use web-proxy credentials for connecting to the endpoint :"?

Use network credentials for connecting to the endpoint: checked
Proxy not checked

What generation method did you use: "Inner" or "SimpleOData"?
Both

What endpoint did you use?

"http://192.168.1.110/ut_kaskad/odata/standard.odata/"

If i try to import whith functions, its generate the same proxy class, but i see error exception
/Unchase.OData.ConnectedService/CodeGeneration/V3CodeGenDescriptor.cs
if (this.ServiceConfiguration.IncludeExtensionsT4File && this.ServiceConfiguration.GenerateFunctionImports)
{
try
{
if (EdmxReader.TryParse(XmlReader.Create(ServiceConfiguration.Endpoint), out var model, out var parseErrors))
functionMethods = FunctionImportsHelper.GetFunctionImportsCode(model, proxyClassName, ServiceConfiguration.Endpoint.Replace("$metadata", string.Empty), this.ServiceConfiguration.FunctionImportsGenerator);
else
{
foreach (var error in parseErrors)
await this.Context.Logger.WriteMessageAsync(LoggerMessageCategory.Warning, error.ErrorMessage);
}
}
catch (Exception ex)
{
await this.Context.Logger.WriteMessageAsync(LoggerMessageCategory.Error, $"Error: {ex.Message}.");
}
}

[gem81]

It seems that at the time of generating functions, the context loses authorization, trying to make an additional request to the server.

[unchase]

Fixed in last commit (v 0.3.14). Please, check the issue.