"Specified native messaging host not found." Errors

580 views
Skip to first unread message

support shift

unread,
Jun 5, 2023, 4:22:36 AM6/5/23
to Chromium Extensions
hello.

First of all, if there is something you do not understand with the translation through Google Translate, please let me know.

When the Windows Registry's native-messaging.json path contains special characters "()"
An error message similar to number 3 below will occur.
However, if you change the Registry path from (TEST) with the special character "()" to TEST minus the special character "()", it will work normally.

Users who use our program do not have permission to install the program in a path other than their user account.
Therefore, our program must be installed in the AppData subfolder of the user account of the user's PC.

If a special character "()" is used in the user account name on the user's PC, the special character "()" is included in the native-messaging.json path of Windows Registry.

I did a Google search for the Windows Registry's native-messaging.json path value, but I couldn't find anything about the restrictions.

Except how to recreate the user account without the special character "()"
I would like to know if there is a way to use it without errors by modifying the program.

1. Windows Registry
[HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.my_company.my_application]
@="C:\\Users\\(TEST)\\AppData\\Local\\Programs\\my_application\\exe\\native-messaging.json"
or
@="C:\\Users\\TEST\\AppData\\Local\\Programs\\my_application\\(exe)\\native-messaging.json"

2. native-messaging.json
{
"name": "com.my_company.my_application",
"description": "My Application",
"path": "MyApp.exe",
"type": "stdio",
"allowed_origins": [
"chrome-extension://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/"
]
}

3. Error Message
Unchecked runtime.lastError: Specified native messaging host not found.

Pavel Aronovich

unread,
Jun 5, 2023, 4:48:34 AM6/5/23
to Chromium Extensions, support shift
Try using escaping "\(".

понедельник, 5 июня 2023 г. в 11:22:36 UTC+3, support shift:
Reply all
Reply to author
Forward
0 new messages