Skip to content

27.1

Links to the API Reference can be found here

27.1.0 (2025-01-21)

Bug Fixes

  • Android: Fix locking of native listeners by using a separate lock mechanism

  • Android: Correct typo in ParkingFacility enum conversion

    This may have caused a crash whenever a POI with this category was returned.

  • Core: Set logistic attribute for VehicleType::Motorhome to ensure proper handling

  • Map: Cache position indicator values instead of making synchronous calls
  • Map: Fix crash when reading an invalid heightmap
  • Map: Fix issues with destroying the map view and camera to prevent memory leaks
  • Map: Improve WCL install progress tracking
  • Navigation: Complete missing road lanes line dividers in lane assistant
  • Navigation: Prioritize highlighting non-overtaking lanes for trucks in the lane assistant
  • Navigation: Fix cycling issue in lane line dividers completion
  • Navigation: Return an empty permanent ID for non-installed voice packages
  • Routing: Assign places to their respective paths correctly
  • Routing: Handle start time overrides correctly
  • Routing: Fix issue with reading places from online HERE Maps
  • Routing: Fix route reconstruction after guided route compute at map borders

Features

  • Android: Add POI visual data to Android interface

    A new Appearance data class was created which is now linked to a ProxyPlaceData object. This class describes the appearance of a corresponding POI in the map.

  • Android: Add option to enforce connector voltage range

    It is now possible to set enforceConnectorVoltageRange in ChargingPreferences.

  • Android: Add waypoint avoids into RoutingOptions

    Waypoints now can be avoided through routingOptions.avoidedWaypoints (list). This is useful if a user wants to avoid a waypoint that was previously calculated through Automatic EV Routing.

  • Android: Deprecate destroy method of PositionSimulator

    This method should not be used and will be deleted in the next major release.

  • Android: Make vehicle profile overrides optional in explore charging station functions

    When calling exploreChargingStationsOnRoute, an option to specify a vehicleProfile is present. However, until now, the method always took the vehicleProfile that was set to the route. From now on, it is possible to override the route's vehicleProfile by specifying a new one that will work only for the explore function. The new option is optional.

  • Core: Allow enforcement of charging connectors with a defined voltage range

  • iOS: Add appearance parameter to SYProxyPlace

    It is now possible to get the visual data of a POI.

  • iOS: Add mapElementsScale parameter to SYMapView initializer

  • iOS: Add waypoint avoids to SYRoutingOptions

    It is now possible to add which waypoints have to be avoided during compute. This is useful if a user wants to avoid a waypoint that was previously calculated through Automatic EV Routing.

  • iOS: Make vehicle profile override in exploreChargingStationsOnRoute function optional

  • iOS: Move start/stopUpdatingPosition from SYPositioning to SYPositioningManager (original methods are marked as deprecated)
  • Map: Add ability to read bus directions from map data for navigation and routing

  • Map: Draw tunnels on roads with distinct set of colors

    The tunnels are now drawn using a slightly different color. It is also possible to change their skin.

  • Map: Render preferred, compatible, and other EVStation POIs differently depending on vehicle profile settings

    Depending on the vehicle profile that is set to the mapView, the Electric charging POIs will be rendered in a different color if they are not suitable for that vehicleProfile.

  • Navigation: Add lane analyzer settings to SDK JSON config

  • Navigation: Adjust highway exit search distances for better accuracy

    The highway exit search in cities and on highways have been changed to 10km and 100km, respectively.

  • Places: Implement caching for online POIs to improve performance

  • Places: Add support for V1 Places API

  • Routing: Validate polyline spacing for guided compute and return an error for incorrect values

    A new error LargeGapInPolyline will now be returned from the routing module if there is a problem with a guided route.

  • Routing: Utilize place position in ComputeRequest