This repository has been archived by the owner on May 9, 2018. It is now read-only.
catch bad token with assertion during development #601
Labels
Comments
incanus
added a commit
that referenced
this issue
Mar 9, 2015
albertschulz
referenced
this issue
in albertschulz/mapbox-ios-sdk
Jun 4, 2015
MarkSpit
referenced
this issue
in MarkSpit/mapbox-ios-sdk
Jun 16, 2015
earltedly
referenced
this issue
in activeintime/mapbox-ios-sdk
Jul 13, 2015
…to release # By Justin R. Miller (12) and others # Via Jason Wray (3) and others * 'release' of https://github.com/mapbox/mapbox-ios-sdk: Strengthen GL language, add Swift Offline example update private header matches bump podspec version updated changelog for 1.6.1 explicit public headers in podspec explicit module name podpsec formatting improvements refs #580: pare down Proj4 headers to barest needed for CocoaPods refs #580: properly find CocoaPods-based resource bundle Smooth edges of user location annotation icon's shadow ensure access token is set for v4 API access update link #578: Unrequire access token for large tiles fixes #601: catch bad token during development fixes #581: properly check for valid offline source Add NSLocationAlwaysUsageDescription check to assert
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When a bad access token is used with the
v4API, the tile source TileJSON comes back bad due to failed access, but this only manifests in an invalid layer to add. We should fail hard here during dev with an assertion to let the dev know.The text was updated successfully, but these errors were encountered: