IssueTracker

Have you looked at using the Asynchronous Loading method https://developers.google.com/maps/documentation/javascript/tutorial#Loading_the_Maps_API ?

Example 1. Just trying to attach your gmaps script.
If you open the developer console, you will see that gmaps init script is loaded, but "getScript("https://maps.gstatic.com/intl/en_us/mapfiles/api-3/9/8/main.js");" line isn't working, there is no new script in the document after document.write.

Example 2. Trying to use callback parameter. Init is loaded, main javascript file is loaded too. But not working, exception screenshot is in attach.

For example 2 - your code:

...
    lf.main = function(a) {
        eval(a);   // <-- Uncaught Error: Code generation from strings disallowed for this context
    };
...

Just to poke this bug, using the asynchronous loading method has no effect on this.  The only workaround is to roll back to manifest version 1 which is actively being phased out.

Switched to Yandex Maps, it works well.
Thank you!

As manifest version 1 won't be accepted by the Chrome Webstore starting in mid August, we really do need a workaround/fix.

As I discovered a few minutes ago, manifest version 1 is no longer accepted by the Chrome store *now*.  So setting the manifest version to 1 and using 'unsafe-eval' in the CSP no longer works for new extensions.

Updating existing extensions may still be supported.

New packaged apps having manifest version 1 are no longer supported.
Please fix this issue as soon as possible.

Thanks

According to deprecation schedule only new items should be affected (for now). For existing items there will be issues starting approximately in November.

Source: http://code.google.com/chrome/extensions/manifestVersion.html

Oh new fun fact, relating to this:  With Chrome 21 you can only install apps/extensions from the Chrome Store.  So not I have an extension I can't deploy to the Chrome Store nor can I push it to my clients directly :(.

Please fix

This is killing now. Can you provide an alternate way to connect to http://maps.google.com/maps/api/js?sensor=false . Thanks

Any updates on this issue or how can we resolve it. If google app cannot support there on google map, that really bad..

Please provide an alternate or a solution ASAP.

Hi all,

A workaround has been released by the Chrome team:
http://code.google.com/chrome/extensions/trunk/sandboxingEval.html

I've attached a sample extension that makes use of this sandboxing technique. To use any of the Chrome extension APIs (e.g. tabs), you'll need to use postMessage to communicate to the popup or background page.