Reply to this email directly, view it on GitHub #2101 (comment), or mute the thread. You are receiving this because you were mentioned. These functionalities can be accessed by typing in the URL and then using the GET, POST, PUT etc HTTP requests. He seems to have forked the old Postman repository and published it as a separate item on the webstore. Postman assist you in testing the functionality you have built into an API. You'll need to contact the published of the unofficial extension for more on this. Postman is available at (the legacy app), and (the currently supported app). Personally, have found the app to be a bit more response and more robust than the chrome extension.You seem to have been using an unofficial build of Postman. Additionally you may consider using the App which can be downloaded directly from If this does work and you get your collections back I would strongly recommend creating an account for Postman and enabling the Sync function. Hopefully this helps you out TiepB5518, good luck! If you don't do this it seems that the "new" install of Postman does not see the collections DB file. Most likely the name of the log file in your "Safe location" will be something like 000258.log and the one in the chrome extension folder will be 000001.log or 000002.log. log extension which windows should identify as a type = Text Document. NOTE: There are a few files named "log" in this folder but only one with a. Rename the log file in this folder to match the name of the log file in your "Safe location".Paste the DB file and the "MANIFEST" file into the clean folder.Copy the DB file and the "MANIFEST" file from your "Safe location" created in step 5.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.I removed the Postman extension and downloaded Postman-linux-圆4-7.14.0.tar. I searched in net and found this article. I tried to run it by clicking on the icon in chrome://extensions/ page. 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) Looks like Postman extension is not supported on Chrome anymore.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) Requestly is an open-source & powerful web debugging tool that allows you to intercept. It was unable to access the internet for some reason. I am sorry I didn't really post all the steps so I am not surprised that you are a bit lost. I had a nearly similar problem, where Chrome postman app (extension) fails to post/get/etc. 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. ReqBin is the worlds most popular online API testing tool for REST, SOAP, and HTTP APIs. After you create the custom Proxy, make sure you turn the Proxy toggle button to off. This article explains how to create a custom proxy. Step 1: In Postman, click the wrench icon, go to settings, then go to the Proxy tab. I guessed that this was because the "current" log files and manifest file where not matching the DB file. When getting the following error, you need to do the following. 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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |