I recently started seeing an exception when calling the geocoder when it's called on a certain page. I'm pretty certain that there is something conflicting with the library, but I'm not quite sure what it is. The call is very simple so it's very surprising that anything else is interfering with the logic.
new google.maps.Geocoder().geocode(
{address:'San Francisco, CA'},
function(results, status){
alert(status);
}
)
This is the stack trace :
Uncaught TypeError: Cannot read property 'value' of undefined VM41132:11
GZ VM41132:11
H.Rm VM41132:18
(anonymous function) VM40916:1
(anonymous function) %7Bmain,places%7D.js:258
(anonymous function) %7Bmain,places%7D.js:887
M %7Bmain,places%7D.js:244
Xf %7Bmain,places%7D.js:886
ag %7Bmain,places%7D.js:925
(anonymous function) VM41132:19
(anonymous function) VM41131:112
(anonymous function) %7Bmain,places%7D.js:896
(anonymous function) %7Bmain,places%7D.js:279
(anonymous function) %7Bmain,places%7D.js:902
M %7Bmain,places%7D.js:244
(anonymous function) %7Bmain,places%7D.js:901
Uf.(anonymous function).cf %7Bmain,places%7D.js:864
Vf.(anonymous function).Yc %7Bmain,places%7D.js:893
Zf %7Bmain,places%7D.js:907
(anonymous function) %7Bcontrols,places_impl,geocoder%7D.js:2
Has anyone run into a similar issue?
EDITED
I guess since no one else have run into this issue, I will use this thread for sharing solution when I have figured it out. I will just have to strip out code block by block until I can narrow down the cause and then figure out what to do with it. It has to be something very simple, but I just have idea where to start. My initial guesses are the following:
- Something is initializing the library before it is ready causing the library to not work properly (same issue as regular Google Maps API with its fall back mode)
- A global variable is changed if it's relying on one