Skip to content

Releases: mapbox/mapbox-java

Mapbox Java SDK v6.0.0

13 Oct 13:15
7bc9a68
Compare
Choose a tag to compare

No additional changes. No issues were identified during testing and the last pre-release has been promoted to stable.

The full list of changes for v6.0.0 is available here.

Mapbox Java SDK v6.0.0-alpha.9

29 Sep 12:21
ffbb755
Compare
Choose a tag to compare
Pre-release

Fixed RouteOptions#toUrl() function. #1302

Mapbox Java SDK v6.0.0-alpha.8

28 Sep 11:11
Compare
Choose a tag to compare
Pre-release
  • Exposed RouteOptions#toUrl() function.

Mapbox Java SDK v6.0.0-alpha.7

23 Sep 20:33
Compare
Choose a tag to compare
Pre-release
  • Exposed include-hov/hot parameters and added exclude list option #1296

Mapbox Java SDK v6.0.0-alpha.6

16 Sep 16:43
Compare
Choose a tag to compare
Pre-release
  • Added support for active_direction encapsulated in lane banner component. #1294

Mapbox Java SDK v6.0.0-alpha.5

01 Sep 18:36
Compare
Choose a tag to compare
Pre-release
  • Added support for layers to RouteOptions object. #1279
  • Added support for missing country code and lanes blocked properties to Incident object. #1288
  • Added support for missing congestion numeric property to LegAnnotation object. #1290

Mapbox Java SDK v6.0.0-alpha.4

26 Aug 12:21
Compare
Choose a tag to compare
Pre-release
  • Added support for metadata response from Directions API. #1282
  • Added max_width and max_height to Directions API params. #1283

Mapbox Java SDK v6.0.0-alpha.3

19 Aug 11:24
f09ceb2
Compare
Choose a tag to compare
Pre-release
  • Bumped okhttp version to 4.9.0. It requires java 1.8 for compatibility. #1271

Mapbox Java SDK v6.0.0-alpha.2

28 Jul 10:27
Compare
Choose a tag to compare
Pre-release
  • Removed accessToken from RouteOptions and moved it to MapboxDirections instead. This simplifies serialization and deserialization of route objects without potential leaks of data under the assumption that an entity that makes a route request has an ability to provide an access token without the route object having to transport it. #1276

Mapbox Java SDK v6.0.0-alpha.1

20 Jul 14:11
692c855
Compare
Choose a tag to compare
Pre-release
  • Refactored MapboxDirections to accept RouteOptions as an argument that defines request parameters #1265
  • ⚠️ Added a List overload in RouteOptions for coordinates, now there are RouteOptions#coordinates(string) and RouteOptions#coordinatesList(list). If there are routes that were previously serialized with toJson methods and contained RouteOptions, they will not be possible to deserialize anymore since coordinates are now stored as a string and not an array. This breaking change can typically impact test fixtures. To address the change in your existing serialized routeOptions, change the coordinates array to a semicolon-separated string, for example:
- "coordinates":[[-122.5237429,37.975393],[-122.5231413,37.9750695]]
+ "coordinates":"-122.5237429,37.975393;-122.5231413,37.9750695"
  • ⚠️ Stopped serializing access tokens. This means that if you're deserializing a route that has routeOptions property, you need to explicitly provide an access token in DirectionsRoute#fromJson(routeJson, accessToken) or an exception will be thrown. #1267
  • Moved the requestUuid object out of RouteOptions and into DirectionsRoute since the UUID is not a request parameter, it's a response value #1265
  • Added enableRefresh to RouteOptions since it is a route request parameter #1265
  • Removed a separate WalkingOptions in favor of storing the parameter directly in the RouteOptions #1265
  • Exposed arriveBy and departAt request parameters #1265
  • Exposed ANNOTATION_CONGESTION_NUMERIC parameter #1265
  • Updated documentation for various route request parameters #1265
  • Exposed DirectionsResponse#fromJson(json, route options, request uuid) that allows to provide information about the original route request which response they deserialize so that Nav SDK can operate correctly #1265
  • Exposed DirectionsRoute#fromJson(json, route options, request uuid) for same reason as above #1265
  • Exposed RouteOptions#fromUrl utility function that creates the object from the request URL which might be useful when paired with the above functions #1265
  • Added default values for RouteOptions: base URL, user, and geometry encoding (polyline6) #1265
    #1265
  • Fixed an issue where coordinates were rounded to 6 decimal places instead of 7 decimal places that the GeoJSON specification expects #1265
  • Changed the default encoding for MapMatching to be polyline6 and aligns it with regular route requests #1265
  • Added a Bearing object that represents a pair of values for {angle, degrees} #1265
  • Removed route request parameters verification in favor of letting the service respond with a correct error #1265
  • Replaced Closure @Nullable annotations with @NonNull #1268