Elsa.Samples.AspNet.DynamicActivityProvider import json error

[erwinx]

Referencing the 3.1.3 package with nuget, the DynamicActivityProvider example imports json errors, and also fails to introduce a custom DynamicActivityProvider at design time. But the latest github source code can't go wrong. When will the next Nuget version be released?

blazor.server.js:1 Uncaught (in promise) Error: Refit.ValidationApiException: Response status code does not indicate success: 400 (Bad Request).
at Refit.RequestBuilderImplementation.<>c__DisplayClass14_02.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 313 --- End of stack trace from previous location --- at Elsa.Studio.Workflows.Domain.Services.RemoteWorkflowDefinitionService.ImportFilesAsync(IEnumerable1 streamParts, CancellationToken cancellationToken)
at Elsa.Studio.Components.StudioComponentBase.InvokeWithBlazorServiceContext[T](Func1 func) at Elsa.Studio.Workflows.Components.WorkflowDefinitionList.WorkflowDefinitionList.OnFilesSelected(IReadOnlyList1 files)
at Elsa.Studio.Components.StudioComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
at Elsa.Studio.Components.StudioComponentBase.InvokeWithBlazorServiceContext(Func1 func) at MudBlazor.MudFileUpload1.NotifyValueChangedAsync()
at MudBlazor.MudFileUpload`1.OnChange(InputFileChangeEventArgs args)
at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
at Ft.endInvokeDotNetFromJS (

[glime-ai]

It seems like you are experiencing issues with importing JSON errors and introducing a custom DynamicActivityProvider at design time using the Elsa 3.1.3 package from NuGet. The error message you provided indicates a 400 (Bad Request) response when trying to import files, which suggests that the request being made to the server is not formatted correctly or the server is rejecting the request for some other reason.

Regarding the release of the next NuGet version, I do not have access to the release schedule for Elsa packages. However, you can keep an eye on the official Elsa NuGet feed or the GitHub repository for updates on new releases. If you need immediate access to the latest fixes, you might consider building the package from the source code available on GitHub.

If you are looking for a more immediate solution to your problem, you could try reaching out to the Elsa community or the maintainers directly through their GitHub issues page or other official communication channels like their Discord server. They might be able to provide you with a workaround or let you know when the next release containing the fix is planned.

Would you like me to provide you with links to the Elsa GitHub repository and NuGet feed for you to monitor updates?

This comment was generated by Glime.