ASP.Net Core 2.1上的Azure移动后端连接问题

Question

I am working on an ASP.Net Core web app and I try to connect it via an Azure Mobile Backend.

The backend is working well with other Windows Desktop applications. Also the backend was working well till now with ASP.Net Core v2.0. Yesterday I installed the ASP.Net Core 2.1 SDK and I updated the Microsoft.AspNetCore.All nuget package from 2.0 to 2.1.2 and since then I am receiving the following exception: MobileServiceInvalidOperationException - "The server did not provide a response with the expected content."

Can you tell me any solution to solve this issue?

Answer 1

Also the backend was working well till now with ASP.Net Core v2.0. Yesterday I installed the ASP.Net Core 2.1 SDK and I updated the Microsoft.AspNetCore.All nuget package from 2.0 to 2.1.2 and since then I am receiving the following exception: MobileServiceInvalidOperationException - "The server did not provide a response with the expected content."

According to your description, your Azure Mobile Backend could work as expected with ASP.Net Core v2.0. AFAIK, mobile backend just provides a simple way for you to expose your Table/API endpoints. Moreover, how did your web app connect with mobile backend, using HttpClient or Azure Mobile Client SDK ?

For a simple way to troubleshoot this issue, you could Enable diagnostics logging for your Azure Mobile App to retrieve the detailed error message to narrow this issue, details you could follow here .

Answer 2

I have the same issue but no solution. I traced it down to the following line of code in MobileServiceHttpClient code in the SendRequestAsync(...) function.

// If there was supposed to be response content and there was not, throw        
if (ensureResponseContent)
{
   long? contentLength = null;

   if (response.Content != null)
   {
      contentLength = response.Content.Headers.ContentLength;
   }

   if (contentLength == null || contentLength <= 0)
   {
        throw new MobileServiceInvalidOperationException("The server did not provide a response with the expected content.", request, response);
   }
}

Looking at the response.Content.Headers.ContentLength it is null . Running the app as a 2.0 Core project, the value is filled in correctly. What is is strange is that the content is there.

If you drill into the private members some of them are set correctly.

catch (MobileServiceInvalidOperationException msioe)
{
    //content will contain the correct json but the ContentLenth is null!?!
    string content = await msioe.Response.Content.ReadAsStringAsync();

}

It is a 2.1 Core issue. Hopefully they fix it.