Removing the "timeout" parameter did the trick! Thanks!
- Scott On Jun 23, 11:05 am, alexg <[email protected]> wrote: > I believe pre-iOS4, mobile safari did not support the additional > timeout parameter in geolocation calls correctly. > > Make sure your code does not contain a timeout of 0 - while OS 3.1.3 > would ignore this value and your app would work, iOS4 now correctly > applies it (as far as I can tell). Either set a timeout of something > other than zero, or remove the parameter and let the browser set the > default timeout period. > > I encountered this in one of my apps after upgrading to iOS4, and > changing this fixed it instantly. > > Regards, > > Alex > > On Jun 23, 2:36 am, Scott Finkelstein <[email protected]> wrote: > > > > > Has anyone here noticed iOS4 breaking their Geolocation web apps? I > > have a page on our web app that plots the users location on a Google > > Map (via the "navigator.geolocation" and "geo_position_js" APIs, > > depending on the user agent). It worked perfectly in iPhone OS 3.1.3, > > but once I updated to iOS 4 I've been getting a "Timeout Expired" > > error message. It worked on my colleague's phone (she didn't update to > > iOS 4 yet) and it also worked on my Desktop via Safari 5. > > > Thanks in advance, > > > - Scott -- You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en.
