ERR - app returned http status code 400 from subscription endpoint

[fbridger]

Expected Behavior

I am having a very weird behaviour when I I debug the ASP.Net Core application from Visual Studio 2019.

The ASP.NET Core application is not being subscribed to any of the Events due to what I believe is a timing problem.

However, if I run the application using dotnet run everything works correctly.

Is this something related to SideKick? the dotnet-sdk? or Dapr Sidecar?

Actual Behavior

The application is not receiving events when it's being Debug from Visual Studio

FAILURE

Logs in DEBUG mode from Visual Studio 2019 (see ERR line)

ERR - app returned http status code 400 from subscription endpoint {SourceContext="Man.Dapr.Sidekick.DaprSidecarHost", DaprVersion="1.3.0", DaprAppId="notifications-api", DaprInstance="MYMACHINE", DaprScope="dapr.runtime", DaprTime="2021-08-25T12:53:40.0125323-03:00", DaprType="log", from="notification-service", ThreadId=15, Version="1.0.0.0", ContainerId="MYMACHINE"}
DBG - app responded with subscriptions [] {SourceContext="Man.Dapr.Sidekick.DaprSidecarHost", DaprVersion="1.3.0", DaprAppId="notifications-api", DaprInstance="MYMACHINE", DaprScope="dapr.runtime", DaprTime="2021-08-25T12:53:40.0125323-03:00", DaprType="log", from="notification-service", ThreadId=15, Version="1.0.0.0", ContainerId="MYMACHINE"}
INF - dapr initialized. Status: Running. Init Elapsed 187.43099999999998ms {SourceContext="Man.Dapr.Sidekick.DaprSidecarHost", DaprVersion="1.3.0", DaprAppId="notifications-api", DaprInstance="MYMACHINE", DaprScope="dapr.runtime", DaprTime="2021-08-25T12:53:40.0345807-03:00", DaprType="log", from="notification-service", ThreadId=15, Version="1.0.0.0", ContainerId="MYMACHINE"}
INF - Dapr Process Status Change: Starting -> Started {SourceContext="Man.Dapr.Sidekick.DaprSidecarHost", from="notification-service", ThreadId=15, Version="1.0.0.0", ContainerId="MYMACHINE"}

SUCCEED

Logs when using DOTNET RUN mode

DBG - app responded with subscriptions [{acme-broker activationcode-for-selfregistered-user Notification/Email/UserRegistrationEmail map[] []} {acme-broker activationcode-for-new-user-added-as-contact Notification/Email/ContactRequireActivationAssociation map[] []} {acme-broker existing-user-added-as-contact Notification/Email/ContactAssociation map[] []} {acme-broker activationcode-for-new-user-added Notification/Email/UserRequireActivationAssociation map[] []} {acme-broker existing-user-associated Notification/Email/UserAssociation map[] []}] {SourceContext="Man.Dapr.Sidekick.DaprSidecarHost", DaprVersion="1.3.0", DaprAppId="notifications-api", DaprInstance="MYMACHINE", DaprScope="dapr.runtime", DaprTime="2021-08-25T12:58:58.623539-03:00", DaprType="log", from="notification-service", ThreadId=4, Version="1.0.0.0", ContainerId="MYMACHINE"}
INF - app is subscribed to the following topics: [activationcode-for-selfregistered-user activationcode-for-new-user-added-as-contact existing-user-added-as-contact activationcode-for-new-user-added existing-user-associated] through pubsub=acme-broker {SourceContext="Man.Dapr.Sidekick.DaprSidecarHost", DaprVersion="1.3.0", DaprAppId="notifications-api", DaprInstance="MYMACHINE", DaprScope="dapr.runtime", DaprTime="2021-08-25T12:58:58.6267787-03:00", DaprType="log", from="notification-service", ThreadId=4, Version="1.0.0.0", ContainerId="MYMACHINE"}

Steps to Reproduce the Problem

Run the application from Visual Studio 2019 in DEBUG mode, launch dapr sidecar using Dapr Sidekick

[badgeratu]

Can you please post to GitHub an example project/solution that illustrates the problem when you run it in Visual Studio? Also when you say you use dotnet run can you confirm you're not invoking that command from the Dapr CLI?

[fbridger]

Sure, I'll create that example in my Sidekick fork and let you know.

Also, I can confirm that I'm not invoking the dapr command. I'm relying on Sidekick to do that .

Thanks for replying @badgeratu

[fbridger]

This is not a Sidekick related issue.

I've created the ticket in dapr/dapr to get some clarifications: https://github.com/dapr/dapr/issues/3598