Navigate back to the path on location on your local machine that you noted in step 3.Postman should open but it will be default settings with none of your collections Remove the Postman extension from Chrome.Copy this entire contents of this folder and save it to a safe location on your local system to be used later (your collections will be in DB file in this folder).Navigate to this location on your local system.Under the "Paths:" section note the location of the "chrome-extension_fhbjgbiflinjbdggehcddcbncdddomop_0.indexeddb.leveldb" folder.Look for: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop.Window 7 (not sure if these steps will work on any other OS)
I am sorry I didn't really post all the steps so I am not surprised that you are a bit lost. So I am now back in business, thanks to the response from Vignesh Anand. After going that I was able to re-launch postman and this time the DB file was not deleted and when postman opened, all my collections were back! To get around this I closed Postman, then copied the DB file and renamed the log file to match the old file. I guessed that this was because the "current" log files and manifest file where not matching the DB file. With a fresh copy of Postman I was able to add back the DB file, but every time that I launched Postman, it would remove the DB, so my collections were missing.
POSTMAN EXTENSION CHROME FREE
Using this information I was able to "copy" the DB file, so I was free to remove Postman and add it back. In the above response Vignesh, shows the location, this was very helpful, because I was concerned about loosing my collections as I was not using the sync option.
At the time I was not able to back up them up and without knowing the location where they are stored locally I was stuck. But I didn't do so because I didn't want to loose my collections. My first thought to fix the crash problem was that I should just remove Postman and add it back.
0 kommentar(er)
