Fix to handle invalid API directions #450
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
On Thursday the 20th (late morning) and Friday the 21st of August NZST a Mapbox API change caused our iOS app to crash on start up when retrieving directions. This was caused by forcibly unwrapping a nil optional in
RoadClasses.swift
(line 102).The change to the API was subsequently rolled back, but it bricked our production app for over a day.
Changes
DirectionsError
which can be handled by the caller, instead of causing a fatal error.Crash Report
Retrieved from Crashlytics: