iOS [iOS 10] MKDirections does not provide route steps or instructions

[hammerfangs]

Hello all, long time lurker, first time poster here.

With iOS 10 in the horizon, I started testing my app on iOS 10 to ensure nothing is broken but I have come across a problem with MKDirections from MapKit. Strangely, I have not seen any official statement/acknowledgement on the behavior nor have I seen reports from the developer community about the bug barring one developer.

Problem: On iOS 10, MKDirections does not provide route steps or instructions. Instructions return null. Results are the same regardless of transportation type.

Reproducibility: This behavior is 100% reproducible on iOS 10.0 and Xcode 8.0 Beta 3 (both on device and iOS 10 simulator). I believe the behavior was the same with Xcode Beta 1 too.

On iOS 9, MKDirections works perfectly fine. I have an app on the App Store that works fine now but is bound to break when iOS 10 is officially released (assuming I am not able to figure this anomaly out by then).

I have submitted a bug report on Apple's Bug Reporter but I have yet to receive any response.

I was just wondering if any one of you have seen similar behavior and know of a solution or have a explanation for the behavior or have received feedback from Apple on the topic.

Many thanks in advance.

 

[hammerfangs]

Anyone?

 

[PhoneyDeveloper]

You should post your question in the iOS beta forum at forums.developer.apple.com. If you don't get an answer there and the next beta comes out and doesn't fix this problem you should send email to apple asking about the status of your bug report. They usually say that it's still under investigation but you should ask anyway.

 

[hammerfangs]

You should post your question in the iOS beta forum at forums.developer.apple.com. If you don't get an answer there and the next beta comes out and doesn't fix this problem you should send email to apple asking about the status of your bug report. They usually say that it's still under investigation but you should ask anyway.

Thank you, PhoneyDeveloper. As it turns out, the issue has been resolved in iOS 10 Beta 4.