umbraco / Umbraco.StorageProviders

MIT License
29 stars 21 forks source link

System.MissingMethodException: Method not found: 'GetExtensionFromUri'. #46

Closed vmachacek closed 2 years ago

vmachacek commented 2 years ago

When I upgraded to v10 i got error coming from Umbraco.StorageProviders.AzureBlob.Imaging.AzureBlobFileSystemImageProvider.IsValidRequest(HttpContext context)

here is full error with stack trace

System.MissingMethodException: Method not found: 'System.String SixLabors.ImageSharp.Web.FormatUtilities.GetExtensionFromUri(System.String)'.
   at Umbraco.StorageProviders.AzureBlob.Imaging.AzureBlobFileSystemImageProvider.IsValidRequest(HttpContext context)
   at SixLabors.ImageSharp.Web.Middleware.ImageSharpMiddleware.Invoke(HttpContext httpContext, Boolean retry)
   at StackExchange.Profiling.MiniProfilerMiddleware.Invoke(HttpContext context) in C:\projects\dotnet\src\MiniProfiler.AspNetCore\MiniProfilerMiddleware.cs:line 119
   at Umbraco.Cms.Web.Common.Middleware.UmbracoRequestMiddleware.InvokeAsync(HttpContext context, RequestDelegate next)
   at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.<>c__DisplayClass6_1.<<UseMiddlewareInterface>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Umbraco.Cms.Web.Common.Middleware.PreviewAuthenticationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next)
   at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.<>c__DisplayClass6_1.<<UseMiddlewareInterface>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Umbraco.Cms.Web.Common.Middleware.UmbracoRequestLoggingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next)
   at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.<>c__DisplayClass6_1.<<UseMiddlewareInterface>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

interestingly this started happening only one of two sites i was upgrading

I was using version 1.1.0 upgrade to 10.0.0 fixed the issue