-
Notifications
You must be signed in to change notification settings - Fork 853
Add support for installing in user profiles on share path #4559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @uvarajkrishna, we'll look into this issue and get back to you. |
Hi, |
@uvarajkrishna is the issue still persistent on the latest version of the app? |
@preethammavin The issue still persists. I checked with version 6.1.3 |
Is there any chance of this issue getting resolved? My Customer's entire organization testers works in a similar VM setup of mine and none could use Postman. |
This is occurring for me, too, on a similar environment under Windows Server 2016 with app-6.7.3 |
Specific info: I have already applied the GPU disabling environment variable. Postman loads (slowly) and I have a few requests saved. After some period of time, new requests fail to work and I cannot open new ones from collections. Dev tools console output (redacted) when I try to open a new request (and it fails silently):
|
Could the issue be in the way that Citrix in particular handles roaming profile sync? |
May be relevant. Node itself or nedb don't like permissions issues in the filestore? |
#4602 may also be relevant here |
Local ops team suggesting mapping the app location to a drive letter and launching it from the drive letter instead of a UNC path. This seems to be helping, at least for the last day. Will keep an eye on it. |
When the issue happening, Git has a similar issue as well. The desktop is using Citrix and roaming profile, |
I am also having a lot of problems using Postman with Folder Redirection and Roaming User Profiles. Almost all versions do not work or stop working after some time (hours to days). Version 9.8.2 works for me, higher and it doesn't work or stops working after some time. |
Description
Recently switched from Chrome extension to Windows Native App. The app would start normally and i was able to create request at the beginning and after some time the Send button wouldn't respond and displays "Sending" state for ever.
The console would show the error "InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing.".
If I try to close the application it wouldn't close properly. So I shall close the app in command prompt using taskkill /F /IM postman.exe.
Now if I open again either through short cut or directly in appdata/Postman folder from command prompt, I get a pop up saying "Could not open Postman. Please contact [email protected]".
My machine is in corporate network VMWare VMs pool with my user profile present in shared path. So part of installation is present in c:/user/myuser/AppData/Local and remaining is present in //sharepath.domain/xxx/profile/yyy/myuser/Application Data
If I delete Postman folder present at share path, I am able to open the application again but the "IDBDatabase': The database connection is closing" issue re-occurs after some time. Especially after i try to save a request in collection or create a collection.
But the same postman application and build version works perfectly fine in my personal laptop with every data stored in my hard drive at c:/user/myuser/AppData/Local and c:/user/myuser/AppData/Roaming
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Application sends the request without any error. If the application is closed and opened again it opens without any issue.
Screenshots
Launch failure

Command line launch outcome

Appdata vs Local App data in windows

Postman console error while sending request or saving collection

Postman console error log
postman-console-error.txt
App information:
Additional context
Tried with latest canary build and the issue would continue to occur.
The text was updated successfully, but these errors were encountered: