Skip to content

Errors.md

Latest commit

 

History

History
111 lines (61 loc) · 2.62 KB

Errors.md

File metadata and controls

111 lines (61 loc) · 2.62 KB

Errors

» You may want to check out the Chrome Docs as well


Failed to start native Messaging host

You may be missing permissions to execute
the application specified with the path value.


Invalid native messaging host name specified

Check f the appId is valid by following the
format described in the Manifest section.


Native host has exited.

The communication interface has broken before
Chrome has read any messages, it is very likely
the fault of the native application.


Specified native messaging host not found.

  • The name specified in the extension may
    differ from the one in the Manifest.

  • The manifests filename may be spelled wrong.

    On Linux and OSX the manifests filename must be the appId.

  • The manifest file may be in the wrong location.

    On Windows make sure the registry key points to the Manifest.

  • The manifest file may not be a proper JSON file.

  • The manifest file may have a JSON syntax error.

  • The manifest file may not use the correct
    key / value pairs as described in Manifest.

  • The file specified in path may not exist.

  • The path may have the wrong type.

    Only Windows allows for relative paths.


Native messaging host appId is not registered.

( Windows Only )

The registry key for the specified appId was missing.
Make sure the key exists and points to the Manifest.


Access to the specified native messaging host is forbidden.

The extensions url may not be listed in allowed_origins ,
please refer to the Manifest on how to format the Id.


Error when communicating with the native messaging host.

Common error indicating an incorrect communication protocol implementation.


  • Check the format of data going to stdout

    Use stderr for debugging.

  • Check the 32-bit message length for
    the platforms native integer format

    little / big-endian

  • A message's length must be < 1024 * 1024

    ( 1,048,576 )

  • Message size == byte count

    Message length may differ when multi-byte encoding is used.

  • (Windows Only)

    By default the IO mode is set to O_TEXT which uses \r\n
    ( 0x0D0A ) instead of \n ( 0x0A ) for line breaks, as such
    please use __setmode to change the IO mode to O_BINARY
    to avoid message corruption.