Fix for Postman + Chrome v34 issue


Some users recently reported that they were unable to start Postman (both packaged and legacy apps) after the new Chrome v34 update. On clicking the app icon, the Postman window opens but neither the history data loads nor are requests sent. The console would show you a bunch of scary errors:

Image 2014-04-10 at 8.23.30 pm

One of our users was kind enough to let me debug this problem through Team Viewer. After digging around, I found out that resetting Chrome flags fixed the issue.

The problem seems to be related to this bug: and is apparently caused by the “Experimental web  platform features” flag.

In r166627 and r166494, we changed CSP 1.1 to block certain CSSOM operations if ‘unsafe-eval’ isn’t present in a ‘style-src’ directive. This seems to be incompatible with the web; it broke every site using jQuery, GitHub, etc.

So, all you have to do is go to chrome://flags and reset everything to defaults. You can try disabling experimental web features too but just to be on the safer side, I would suggest resetting everything.

If you are still facing problems in starting Postman, feel free to reach out on Twitter or Github.



Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

1 thought on “Fix for Postman + Chrome v34 issue


    I’ve reset all the flags and I’m still not able to launch Postman. My chrome version is 34.0.1847.131.