search

Azure / azure-functions-signalrservice-extension

Azure Functions bindings for SignalR Service. Project moved to https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/signalr/Microsoft.Azure.WebJobs.Extensions.SignalRService .
MIT License
96 stars 48 forks source link

Unsupported service transport type #156

Closed gavinsteinhoff closed 3 years ago

gavinsteinhoff commented 3 years ago

I keep getting this message when my C# function app is starting.

Unsupported service transport type: . Use default Transient instead.

I have a basic function app setup to use signalR:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
      <TargetFramework>netcoreapp3.1</TargetFramework>
      <AzureFunctionsVersion>v3</AzureFunctionsVersion>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Mvc.Core" Version="2.2.5" />
    <PackageReference Include="Microsoft.Azure.Functions.Extensions" Version="1.1.0" />
    <PackageReference Include="Microsoft.Extensions.Options.DataAnnotations" Version="5.0.0" />
    <PackageReference Include="Microsoft.NET.Sdk.Functions" Version="3.0.11" />
    <PackageReference Include="Microsoft.Azure.WebJobs.Extensions.SignalRService" Version="1.2.2" />
  </ItemGroup>

I can still negotiate with the signalR service, but I would like to figure out why this message is here.

Azure Functions Core Tools
Core Tools Version:       3.0.3160 Commit hash: 00aa7f43cc5c5f15241b5e6e5363256f19ceb990
Function Runtime Version: 3.0.14916.0
...
[2020-12-29T16:30:41.028Z] Services registered by external startup type Microsoft.Azure.WebJobs.Extensions.SignalRService.SignalRWebJobsStartup:
[2020-12-29T16:30:41.031Z]  Microsoft.Azure.WebJobs.Host.Config.IExtensionConfigProvider: Implementation: Microsoft.Azure.WebJobs.Extensions.SignalRService.SignalRConfigProvider, Lifetime: Singleton
[2020-12-29T16:30:41.033Z]  Microsoft.Extensions.Options.IConfigureOptions`1[[Microsoft.Azure.WebJobs.Extensions.SignalRService.SignalROptions, Microsoft.Azure.WebJobs.Extensions.SignalRService, Version=1.2.2.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]]: Factory, Lifetime: Singleton
[2020-12-29T16:30:41.227Z] Active host changing from '(null)' to 'b6f82d15-61e0-443a-a55e-7c4f36fdcc3f'.
[2020-12-29T16:30:41.393Z] Workers Directory set to: C:\Users\b1116579\AppData\Local\AzureFunctionsTools\Releases\3.16.1\cli_x64\workers
[2020-12-29T16:30:41.654Z] Initializing Warmup Extension.
[2020-12-29T16:30:41.661Z] Unsupported service transport type: . Use default Transient instead.

When I use the source code for Microsoft.Azure.WebJobs.Extensions.SignalRService, this message doesn't appear. Just when targeting the NuGet package.

zackliu commented 3 years ago

Don't worry. It's because you didn't set AzureSignalRServiceTransportType in config. I think the log content is not such clear.

Y-Sindo commented 3 years ago

The fix is released in 1.3.0

mgwilliam commented 2 years ago

I get this issue with 1.6.0

Y-Sindo commented 2 years ago

@mgwilliam Could you provide us with the complete log message?

mgwilliam commented 2 years ago

from app insights:

"AzureSignalRServiceTransportType not set, using default Transient instead."

Y-Sindo commented 2 years ago

from app insights:

"AzureSignalRServiceTransportType not set, using default Transient instead."

This is an information level message; I think you could just ignore it. We will remove this log in the next release.