Android SDK changelog

SDK v1.5.x (Stable Version: 1.5.6)

v1.5.13

  • Fixes NullPointerException crash in BatteryState.getBatteryPercentage()
  • Fixes OutOfMemoryError crash in MqttInputStream.readMqttWireMessage()

v1.5.12

  • Adds Fcm Integration to DriverSDK: With these release, the DriverSDK now supports FCM integration along with GCM. FCM/GCM Integration adds robustness to backend-start and decreases the time to first location significantly. Refer to the Enabling Gcm/Fcm Integration guide for detailed info.

v1.5.9 - v1.5.10

  • Bug Fixes & Improvements

v1.5.8

  • Adds Gcm Integration to DriverSDK: With these release, the DriverSDK now supports GCM integration. GCM Integration adds robustness to backend-start and decreases the time to first location significantly. Refer to the Enabling Gcm Integration guide for detailed info.

v1.5.7

  • Adds Offline State management to DriverSDK: With the current release, a notion of state has been added where the SDK would keep a track of a driver's Active Trip & Shift. In case of Offline EndTrip call, the DriverSDK's LocationService would be stopped provided the driver didn't have a Shift active at that moment.

v1.5.6

  • Fixes OutOfMemory (OOM) crashes: On certain devices, We've observed that the device goes into OOM scenario while posting data to the server. These crashes will now be caught with the current changes. In the meanwhile, we're working on optimizations to fix such OOM issues.
  • Bug fixes and improvements

v1.5.5

  • Bug fixes and improvements

v1.5.4

  • Fixes default values for isAutoEnded & hasOrderedTasks flags in HTTripParamsBuilder: With these changes isAutoEnded & hasOrderedTasks flags will not take any default values in the DriverSDK unless specified.
  • Adds TransmitterErrorCallback as a parameter in connectDriver() API: With SDK v1.5.4 the connectDriver API also supports a TransmitterErrorCallback param which specifies the integration or validation errors in DriverSDK.
  • Fixes startLocationService API's onSuccess callback not getting called issue

v1.5.2 (Requires Integration Changes)

  • API callback structure has been modified to streamline Offline Response Handling along with few API additions, modifications and deletion. Refer to the upgrading guide for detailed info.
  • Upgrades targetSDKVersion, buildToolsVersion and android-support library version to support Android N (API 25)
  • Upgrades google-play-services to 10.0.1
  • Fixes issues with cached requests including using isAutoEnded, hasOrderedTasks flags for cached startTrip
  • Adds driverID in Service start and stop broadcasts

v1.5.1

  • Fixes JsonSyntaxException & ParseException in completeTask & endTrip cached requests: We observed crashes on certain devices while processing the cached requests. This issue has been fixed with these changes.
  • Fixes NullPointerException in HTMqttClient while subscribe issue: With these changes, a corner case issue has been fixed where mqttClient was null while the subscription to a topic was attempted using this client.

SDK v1.4.x

v1.4.20

  • Fixes null driverID for startTrip if not specified issue: We observed that if driverID is not specified in startTrip API parameters, one is auto-generated on the backend. This is an issue in the scenario where a cached driverID already exists on the DriverSDK and it has been fixed with these changes.

v1.4.19

  • Fixes DriverSDK subscribed to multiple DriverIDs: We observed that if the driverID gets updated on the app on runtime (for ex: prompted by a fresh driver login), the MQTTClient is still subscribed to receive commands for last configured DriverID. This leads to the DriverSDK receiving commands for multiple drivers simultaneously. This issue has been fixed with these changes.
  • Fixes caught NullPointerException while subscribing to a topic

v1.4.18

  • No Changes

v1.4.16

  • Fixes NullPointerException in AlarmManager.cancel() on Android 7.1.1

v1.4.14

  • Fixes multiple calls to connect to MQTT Client

v1.4.11 - v1.4.13

  • Minor bug fixes and improvements

v1.4.10

  • Fixes SDK re-initialization when driver id is updated
  • Minor bug fixes and improvements

v1.4.9

  • Fixes MQTT Connectivity Issues: We observed that MQTT Connection was having issues in patchy and offline network conditions. These changes fix the MQTT Connection settings which were resulting in such issues.
  • Adds isDriverConnected API in HTTransmitterService: Call isDriverConnected API to check whether the driver is currently connected to the Server to receive commands or not. Refer to Checking DriverSDK Status section for more info.
  • Minor bug fixes & improvements

v1.4.8

  • Fixes ConcurrentModificationException crash in MQTT Client
  • Fixes NullPointerException in HTJobScheduler.isJobValid()
  • Improvements in Offline Handling of SDK in patchy network conditions

v1.4.7

  • Improvements in Offline Handling of SDK
  • Minor Bug Fixes and Improvements

v1.4.6

  • Fixes crash in BroadcastReceivers
  • With SDK versions 1.4.x, We observed crashes if HTTransmitterService is initialized in BroadcastReceiver's onReceive() method. This crash has been fixed with these changes.

v1.4.5

  • Adds Driver's Current Location Broadcast
  • The LocationService is responsible for collecting locations in DriverSDK. There might arise a use-case where driver's current location needs to be used. So with this release, a Broadcast has been added in DriverSDK which will broadcast driver's location updates. Refer to Handling DriverSDK Intents section for more info. You can also refer to the example implementation in our example-android app.

v1.4.4

  • Major modifications in the HTTransmitterService APIs (breaks integration)
  • There have been a few API additions, modifications and deletion. Refer to the upgrading guide for detailed info.

results matching ""

    No results matching ""