NativeMessaging addon with error in console: "Attempt to postMessage on disconnected port"

[daniell (daniellplasma@gmail.com)]

Related posts:

Native-messaging API--catching a connection request failure versus a genuine disconnection

Thanks. I’m not trying to complain about it, if it comes across like that. Regardless of whether or not the request for a port was successful, nativeApp.port.error is null immediately after the request. The onDisconnect event does fire and at that stage the value is No such native application NatAppName. nativeApp.port = browser.runtime.connectNative( "NatAppName" ); console.log( nativeApp.port ); // This won't work. if ( nativeApp.port.error ) { console.log( "Error connecting to nat…

Native-messaging API---bytes or characters or both for message measurements?

In the native-messaging API, where it reads, Each message is serialized using JSON, UTF-8 encoded and is preceded with a 32-bit value containing the message length in native byte order. The maximum size of a single message from the application is 1 MB. The maximum size of a message sent to the application is 4 GB. does this mean that the 32-bit value provides the length as number of characters and the maximum size is 1 MB in bytes regardless of the number of characters? I tried to read whe…

With good answers from: @hans_squared and @juraj.masiar
(hope they can help here, too).