Skip to content

Debugger.js exception for HTTP requests with no Content-Type #4419

Closed

Description

@milannankov

Hello,

I am getting an error in debugger.js when debugging my app. The app sends HTTP requests some of which happen to have no "Content-Type". This seems to be causing the error.

Error: Error while parsing debug 'response' object. mimeType: string value expected.

Debugger.ts contains the following code:
let mimeType: string = <string>headers["Content-Type"] || <string>headers["content-type"];

So there will be no mimeType for requests with no "Content-Type". Locally I have temporarily fixed the problem by providing an empty string if no "Content-Type" is specified.

let mimeType: string = <string>headers["Content-Type"] || <string>headers["content-type"] || '';

Which platform(s) does your issue occur on?

Android

Please provide the following version numbers that your issue occurs with:

  • CLI: 3.0.3

  • Cross-platform modules: 3.1.0-2017-06-16-6999 or 3.0.1

  • Runtime(s): 3.0.1

Please tell us how to recreate the issue in as much detail as possible.

  1. Unzip the sample
  2. Run the http server - node .\server\index.js
  3. Add Android platform to the app - HelloWorld
  4. Update main-page.js to hit the correct URL
  5. Run the app in debug mode using VS Code
  6. Click the button

bug-http.zip

Activity

  1. NickIliev commented on Jun 19, 2017

    @NickIliev
    Contributor

    The issue is only reproducible when using local node server (as in the posted example above).

  2. joshcomley commented on Jun 26, 2017

    @joshcomley
    Contributor

    I have the same issue, with the same environment as @R4ZuL

  3. joshcomley commented on Jun 26, 2017

    @joshcomley
    Contributor

    Hacky fix for now, I just modified line 15 of debugger.js in my node_modules to:

        var mimeType = headers["Content-Type"] || headers["content-type"] || "text/plain";
    
  4. added a commit that references this issue on Aug 25, 2017
  5. added this to the milestone on Aug 25, 2017
  6. added a commit that references this issue on Aug 25, 2017
  7. lock commented on Aug 28, 2019

    @lock

    This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

  8. locked and limited conversation to collaborators on Aug 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions