DirectionsError

There is no network connection available to perform the network request.

The server returned an empty response.

The API recieved input that it didn’t understand.

The server returned a response that isn’t correctly formatted.

No route could be found between the specified locations.

Make sure it is possible to travel between the locations with the mode of transportation implied by the profileIdentifier option. For example, it is impossible to travel by car from one continent to another without either a land bridge or a ferry connection.

The specified coordinates could not be matched to the road network.

Try again making sure that your tracepoints lie in close proximity to a road or path.

The request specifies too many coordinates.

Try again with fewer coordinates.

A specified location could not be associated with a roadway or pathway.

Make sure the locations are close enough to a roadway or pathway. Try setting the Waypoint.coordinateAccuracy property of all the waypoints to nil.

Unrecognized profile identifier.

Make sure the DirectionsOptions.profileIdentifier option is set to one of the predefined values, such as ProfileIdentifier.automobile.

The request is too large.

Try specifying fewer waypoints or giving the waypoints shorter names.

Too many requests have been made with the same access token within a certain period of time.

Wait before retrying.

The current route may no longer be refreshed.

Route’s refresh TTL has expired and it is not possible to refresh it anymore. Try requesting a new one instead.

Unknown error case. Look at associated values for more details.