I found the issue and corrected it. The sample code that I was using as reference in the Premium API guide stated
Supply your client ID and sensor parameter as properties of your Map object directly within ActionScript code: var map:Map = new Map(); map.sensor = false; map.client = "gme-yourclientid"; This method is necessary if you are developing your application within Flash CS3. map.sensor = "false"; is the correct method. On Sep 17, 7:37 pm, "Thor Mitchell (Google Employee)" <[email protected]> wrote: > Hi all, > > We are in the process of releasing v1.19 of the Maps API for Flash, > and I wanted to give you all a heads up of a change that will affect > your apps when you come to rebuild them against v1.19 or later. > > As of v1.19, all Maps API for Flash applications will be required to > declare whether the application relies on the device that runs the app > providing the user's location from a sensor such as used by phones > that support GPS geolocation. You should declare this in your apps by > setting the sensor parameter in the same way that you set the Maps API > key. You can see examples of how to set the sensor parameter in the > Maps API Premier docs (we are working on updating the other docs): > > http://code.google.com/apis/maps/documentation/premier/guide.html#Sensorhttp://code.google.com/apis/maps/documentation/premier/guide.html#Flash > > Apps built against 1.19 that do not set the sensor parameter will > display a warning when launched. Existing apps built prior to 1.19 > will be unaffected. > > Use of the sensor parameter has been mandatory in the v3 JavaScript > API since launch, but we have not needed to enforce it in the Maps API > for Flash until now because Flash was not supported by the class of > devices concerned. However with the recent launch of Flash for Android > we now have to also extend this requirement to the Maps API for Flash. > > Note that the value of the sensor parameter has no impact whatsoever > on the features, functionality, or quotas for your application (ie. > there is no reason not to declare honestly if you are relying on such > a sensor). We need this information because it affects our financial > obligations to the companies from which we license the data on which > our maps are based, and we would therefore need to take action to > prevent access to the API by any app that falsely declares that it is > not using a sensor. > > We'll have more information on the other changes in v1.19 for you > early next week. > > Many thanks, > > Thor Mitchell > Product Manager > Google Maps API -- You received this message because you are subscribed to the Google Groups "Google Maps API For Flash" 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/google-maps-api-for-flash?hl=en.
