Native Messaging Host issue in Edge 80/81

%3CLINGO-SUB%20id%3D%22lingo-sub-1152976%22%20slang%3D%22en-US%22%3ENative%20Messaging%20Host%20issue%20in%20Edge%2080%2F81%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1152976%22%20slang%3D%22en-US%22%3E%3CP%3ETrying%20to%20test%20our%20extension%20in%20Edge%2080%2F81%20and%20having%20trouble.%26nbsp%3B%20The%20NMH%20process%20starts%2C%20but%20after%20a%20few%20messages%20are%20exchanged%2C%20the%20pipe%20is%20closed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoftedgeinsider.com%2Fen-us%2Fwelcome%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EBeta%20welcome%20page%3C%2FA%3E%26nbsp%3Blists%20a%20known%20issue%20with%20webstore%20extensions%20%22The%26nbsp%3B%3CSPAN%3EIf%20an%20extension%20relies%20on%20companion%20software%20on%20your%20PC%2C%20it%20may%20not%20work%20properly%2C%20even%20if%20the%20companion%20software%20is%20installed.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIn%20my%20case%2C%20I%20am%20working%20in%20developer%20mode%2C%20loading%20an%20unpacked%20extension%20but%20the%20known%20issue%20description%20sounds%20suspicious.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20extension%20is%20working%20fine%20in%20the%20Stable%20release%20of%20Edge%2079%20(and%20also%20works%20in%20Chrome%2079%2C%2080%2C%20and%2081).%26nbsp%3B%20Does%20anyone%20have%20any%20idea%20what%20might%20be%20happening%20in%20the%20beta%20or%20have%20any%20details%20related%20to%20the%20known%20issue%20above%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1153607%22%20slang%3D%22en-US%22%3ERe%3A%20Native%20Messaging%20Host%20issue%20in%20Edge%2080%2F81%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1153607%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F546138%22%20target%3D%22_blank%22%3E%40CConti%3C%2FA%3E%26nbsp%3BWe're%20sorry%20to%20hear%20that%20you're%20running%20into%20some%20roadblocks%20above%2079.%20Can%20you%20please%20confirm%20exactly%20which%20channels%20and%20versions%20didn't%20work%3F%20And%20if%20you%20have%20an%20error%20log%2C%20please%20submit%20it%20through%20the%20browser%20for%20the%20devs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)Project%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1155901%22%20slang%3D%22en-US%22%3ERe%3A%20Native%20Messaging%20Host%20issue%20in%20Edge%2080%2F81%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1155901%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20testing%20with%20The%20Beta%20Channel%20(Version%2080.0.361.47%20(Official%20build)%20beta%20(64-bit)).%26nbsp%3B%20Saw%20the%20same%20behavior%20with%20the%20Dev%20Channel%20(don't%20currently%20have%20it%20installed%2C%20didn't%20create%20a%20snapshot%20in%20my%20VM%2C%20but%20it%20was%20the%20current%20version%20of%2081%20as%20Monday%202%2F5)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20much%20in%20the%20way%20of%20logs%20(Is%20there%20any%20additional%20logging%20that%20can%20be%20turned%20on%20in%20regards%20to%20native%20messaging%20hosts%3F).%26nbsp%3B%20The%20only%20error%20in%20the%20console%20is%20'Unchecked%20runtime.lastError%3A%20Error%20when%20communicating%20with%20the%20native%20messaging%20host.'%26nbsp%3B%20Yes%2C%20I%20can%20handle%20the%20error%20when%20it%20occurs%2C%20but%20at%20that%20point%20the%20stdio%20pipe%20has%20already%20been%20closed.%26nbsp%3B%20This%20happens%20after%20the%20NMH%20process%20has%20been%20launched%20and%20several%20messages%20have%20already%20been%20exchanged.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1157336%22%20slang%3D%22en-US%22%3ERe%3A%20Native%20Messaging%20Host%20issue%20in%20Edge%2080%2F81%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157336%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F546138%22%20target%3D%22_blank%22%3E%40CConti%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20details.%20If%20you%20use%20the%20%22submit%20feedback%22%20icon%20in%20the%20browser%2C%20it%20will%20capture%20diagnostic%20data%20and%20logs%20(with%20your%20permission)%20and%20send%20them%20to%20our%20devs.%20While%20I'd%20still%20recommend%20doing%20that%2C%20I%20will%20also%20loop%20in%20our%20extension%20team%20and%20let%20you%20know%20if%20they%20can%20have%20any%20additional%20insights%20or%20questions.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)Project%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1157441%22%20slang%3D%22en-US%22%3ERe%3A%20Native%20Messaging%20Host%20issue%20in%20Edge%2080%2F81%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157441%22%20slang%3D%22en-US%22%3EThanks%20for%20looping%20me%20in.%20I%20did%20submit%20feedback%20around%2011%3A00EST%20this%20morning.%20(I%20don't%20see%20any%20kind%20of%20tracking%20number%20on%20the%20confirmation%20email%20to%20paste%20here)%3CBR%20%2F%3E%3CBR%20%2F%3ECConti%3C%2FLINGO-BODY%3E
New Contributor

Trying to test our extension in Edge 80/81 and having trouble.  The NMH process starts, but after a few messages are exchanged, the pipe is closed.

 

The Beta welcome page lists a known issue with webstore extensions "The If an extension relies on companion software on your PC, it may not work properly, even if the companion software is installed."

 

In my case, I am working in developer mode, loading an unpacked extension but the known issue description sounds suspicious.

 

The extension is working fine in the Stable release of Edge 79 (and also works in Chrome 79, 80, and 81).  Does anyone have any idea what might be happening in the beta or have any details related to the known issue above?

4 Replies

@CConti We're sorry to hear that you're running into some roadblocks above 79. Can you please confirm exactly which channels and versions didn't work? And if you have an error log, please submit it through the browser for the devs.

 

Fawkes (they/them)
Project & Community Manager - Microsoft Edge

@Deleted 

Currently testing with The Beta Channel (Version 80.0.361.47 (Official build) beta (64-bit)).  Saw the same behavior with the Dev Channel (don't currently have it installed, didn't create a snapshot in my VM, but it was the current version of 81 as Monday 2/5)

 

Not much in the way of logs (Is there any additional logging that can be turned on in regards to native messaging hosts?).  The only error in the console is 'Unchecked runtime.lastError: Error when communicating with the native messaging host.'  Yes, I can handle the error when it occurs, but at that point the stdio pipe has already been closed.  This happens after the NMH process has been launched and several messages have already been exchanged.

@CConti Thanks for the details. If you use the "submit feedback" icon in the browser, it will capture diagnostic data and logs (with your permission) and send them to our devs. While I'd still recommend doing that, I will also loop in our extension team and let you know if they can have any additional insights or questions.

 

Fawkes (they/them)
Project & Community Manager - Microsoft Edge

Thanks for looping me in. I did submit feedback around 11:00EST this morning. (I don't see any kind of tracking number on the confirmation email to paste here)

CConti