From 0fef00737190e51d9f5fcd816c52a74c8676e006 Mon Sep 17 00:00:00 2001
From: 5bentz <10729484+5bentz@users.noreply.github.com>
Date: Sun, 3 Jun 2018 09:40:47 +0200
Subject: [PATCH] Doc: Add Advanced Troubleshooting section

  - Debugging mode (in PassFF)
  - Version check
  - Output check
---
 README.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/README.md b/README.md
index 4c14c6e..94dccec 100644
--- a/README.md
+++ b/README.md
@@ -129,6 +129,21 @@ When the PATH variable is not set correctly, `pass` will complain about not find
 PATH="$(which bash | xargs dirname)" $(which pass)
 ```
 
+### Advanced Troubleshooting
+If nothing above has worked out your issue...
+
+#### Gather information in the web browser
+In the preferences of PassFF, you can enable the status bar and debug logs in the Web Console (to open the console: Ctrl+Shift+K in Firefox, Ctrl+Shift+J in Chrome/Chromium). Enable the debugging mode in `about:debugging`, and reload the app.
+
+#### Make sure the version of the host application is supported by PassFF
+* Open the `passff.py` file to find its version number
+  * `head /path/to/passff.py`
+
+#### Check the output of the host app
+* Run `echo -e "\x02\x00\x00\x00[]" | /path/to/passff.py | tail -c +4; echo`
+* The typical output for an empty store is:
+  * `{"stderr": "", "version": "1.0.1", "exitCode": 0, "stdout": "Password Store\n"}`
+
 ### Preferences
 By modifying the `preferences section` in `passff.py` you will be able to set
   - the path to the `pass` script,