From 8faefe43af1417f3fca724e19754a916e14c4fac Mon Sep 17 00:00:00 2001 From: Chad Scharf <3904944+cscharf@users.noreply.github.com> Date: Thu, 15 Jul 2021 16:42:26 -0400 Subject: [PATCH] Update manifest info in readme.md for desktop comm Prior PR that I approved and merged in needed a little bit more info that Oscar had pointed out to help with other OS's regarding manifest locations such as macOS. This is not an exhaustive reference but at least points the person in the right direction. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 722ab860f7..e0737e18a7 100644 --- a/README.md +++ b/README.md @@ -49,7 +49,7 @@ Native Messaging (communication between the desktop application and browser exte Out of the box, the desktop application can only communicate with the production browser extension. When you enable browser integration in the desktop application, the application generates manifests which contain the production IDs of the browser extensions. To enable communication between the desktop application and development versions of browser extensions, add the development IDs to the `allowed_extensions` section of the corresponding manifests. -Manifests are located in the `browser` subdirectory of the Bitwarden configuration directory. For instance, on Windows the manifests are located at `C:\Users\\AppData\Roaming\Bitwarden\browsers`. Note that disabling the desktop integration will delete the manifests, and the files will need to be updated again. +Manifests are located in the `browser` subdirectory of the Bitwarden configuration directory. For instance, on Windows the manifests are located at `C:\Users\\AppData\Roaming\Bitwarden\browsers` and on macOS these are in `Application Support` for various browsers ([for example](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_manifests#manifest_location)). Note that disabling the desktop integration will delete the manifests, and the files will need to be updated again. # Contribute