ios6-maps

Before IOS 6, I was using this URL scheme to open the native maps app and find directions from the users current location to an address that I created. http://maps.google.com/maps?daddr= " + address + "&saddr=Current+Location This was working great, but now that they got rid google maps with IOS 6, we had to check which IOS version they were on and then refer them to the new apple maps url scheme if they were using IOS 6.0 or greater. The new url scheme we are using is this.... http://maps.apple.com/maps?daddr= " + address + "&saddr=Current+Location This is based on the new documentation for

I've an app on the apple store and after the iOS6 update I've got hundred of crash report within MKMapView . I cannot manage to reproduce the crash on my devices. It looks like a problem with EAGLContext . We don't use OpenGL in our app but we have more than one instances of MKMapView in different controller. I've found a similar issue here iOS 6 app crashes in EAGLContext when displaying maps but they use OpenGL. Here there is the backtrace: Exception Type: SIGSEGV Exception Codes: SEGV_ACCERR at 0x1 Crashed Thread: 0 Thread 0 Crashed: 0 libGPUSupportMercury.dylib 0x00000e22 gpus

I am using GoogleMap API for showing draw direction between two points on GoogleMap. i want to give support on iOS 6.1 so i use GoogleMap i know about iOS7 recover this. using below code for parsing and get Steps for coordinates to draw polyline on Map: NSString *str=@"http://maps.googleapis.com/maps/api/directions/json?origin=bharuch,gujarat&destination=vadodara,gujarat&sensor=false"; NSURL *url=[[NSURL alloc]initWithString:[str stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding]]; NSURLRequest *request = [NSURLRequest requestWithURL:url cachePolicy

Almost every major news media outlet is reporting that Apple will stop using Google Maps services in iOS6. I don't think anyone really knows what exactly the changes are, when they will be rolled out, how Apple will implement them and if Google or Apple will start charging money for their services. As a result of these uncertainties, I am having trouble making a sound decision on whether I should or should not release a new public bus tracker app that I have been working on for over a year now. I have had the initial hard deadline set for June 15, 2012. I know that the best thing to do is to

Has anyone else, who's using maps in their iOS 6 apps, noticing extremely high memory use to the point of receiving memory warnings over and over to the point of crashing the app? I've ran the app through instruments and I'm not seeing any leaks and until the map view is created the app consistently runs at around ~3mb Live Bytes. Once the map is created and the tiles are downloaded the Live Bytes jumps up to ~13mb Live Bytes. Then as I move the map around and zoom in and out the Live Bytes continuos to climb until the app crashes at around ~40mb Live Bytes. This is on an iPhone 4 by the way.