-
Notifications
You must be signed in to change notification settings - Fork 853
Postman stuck on splash screen after update #4642
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
Same here, the problem seems incompatibility with the old database. you can delete the postman dir in Application Support. It launches but of course is empty. This is very annoying as i lost al my data. |
@alanatkinson can you share the complete logs from devtools? You can This will give us a complete picture of what goes wrong. |
Same thing happening on Arch Linux with https://aur.archlinux.org/packages/postman/ after upgrading to 6.1.3 |
Same on ArchLinux. Even after deleting config, reinstalling the app. Sudo also not working. |
Same under Windows as well, I'm stuck on the splash screen. |
@suur @lukasz-gosiewski The link you provided is not officially supported by Postman. We support the platforms listed here And @WurstCommander Kindly provide me more information on this. |
@alanatkinson can you confirm that this issue still persists in the latest version 6.1.4 version of the app. |
No I can't. |
@SamvelRaja The link I provided is a basically a repackaging script for the official binaries. I can confirm 6.1.4 works again on Arch Linux, although I have deleted my config. 6.1.3 did not work even with a fresh config. |
Postman 6.0.10 was running fine until today I clicked update to 6.1.4. Postman wouldn't start. Symptoms:
Somewhere in this process, I also started postman 6.1.4 from the CMD. I Attached the console output. My environment: Windows 8.1x64 with latest updates, GPU NVIDIA GeForce 940M EDIT I just now found issue #4594 and can confirm, the workaround using the environmen variable solves the issue for me and Postman 6.1.4 is now working. |
@ssjena @gabriel-bronfman-postman Could you open the app via |
Hi @SamvelRaja ,
|
@ssjena Can you show the logs generated in cmd when you open the app. |
i got it resolved now . I have deleted all postman stuff from local,roaming folder in C drive and reinstalled it and worked. Thanks |
Yesterday the bug was back, I had the close the postman.exe with taskmanager and at last postman started. |
A year has passed and I still have this issue. related: #4605 |
Should be something wrong with workspace data. After i clean up the workspace, it looks fine. |
Hey @blowsie Sorry for the delayed response. We'd like some more information to debug this issue better.
You can find the logs using
|
@kamalaknn thanks for the response. I fixed it by deleting
|
After self-upgrading to 6.1.3 on a Mac running High Sierra 10.13.4 the postman app fails to get past the launch screen regardless of how long one waits.
The last thing you see is "Preparing your workspaces... This may take a few minutes"
The log from devtools shows the following:
Uncaught (in promise) Error: Callback was already called.
at vendor-shared.js:100559
at vendor-shared.js:125393
at initializeServices.then.catch.e (shared.js:8747)
at
Trying it with Canary, it at least launches, but then you lose all your local saved calls. Which is problematic.
The text was updated successfully, but these errors were encountered: