You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Postman for Windows
Version 6.2.3
Windows 10 / x64
Issue Report:
Immediately following the autoamtic update to v6.2.3 widows postman app has stopped working and will not launch correctly.
Instead of getting to the main UI it gets stuck at the launch screen with the three circles and does not progress.
When view the DevTools > current View can see there is an error being reported for........ 1533550453634.log
Downgraded to v6.1.4 and this issue goes away but immediately then forced to re-upgrade to v6.2.3 as no way to turn off the auto update to this version making is unusable.
The text was updated successfully, but these errors were encountered:
Immediately following the autoamtic update to v6.2.5 widows postman app has stopped working and will not launch correctly.
Instead of getting to the main UI it gets stuck at the launch screen with the three circles and does not progress.
When view the DevTools > current View can see there is an error being reported
When view the DevTools > shared View can see there is an error being reported
Could some one Please let me know, how to resolve this issue.
I have Contacted your colleague and i have tried all her steps but still i have this issue
Note:When i go back to previous version which i had 5.1.2, its working fine
App Details:
Issue Report:
Immediately following the autoamtic update to v6.2.3 widows postman app has stopped working and will not launch correctly.
Instead of getting to the main UI it gets stuck at the launch screen with the three circles and does not progress.
When view the DevTools > current View can see there is an error being reported for........
1533550453634.log
Downgraded to v6.1.4 and this issue goes away but immediately then forced to re-upgrade to v6.2.3 as no way to turn off the auto update to this version making is unusable.
The text was updated successfully, but these errors were encountered: