Releases: hypertrack/sdk-android
Releases · hypertrack/sdk-android
7.2.0
Added
- Uses NTP servers to synchronize time independantly from the OS. Avoids sending data with wrong time information for users who override phone's settings with incorrect values.
Fixed
- Mitigates SDK cache file corruption that led to some Android devices loading to device_id values with all zeroes.
- Reduced network traffic.
7.1.0
Added
- Dynamic publishable key API
7.0.11
Changed
- Added more comprehensible error message for the case when one of the SDK plugins is missing
7.0.10
Fixed
- Crash when setting the name with non-ASCII characters
- Freeze on canceling the subscription multiple times
7.0.9
Fixed
- Unicode representation of strings (to address crashes in case of non-unicode symbols in device name)
7.0.8
Fixed
- This version of the SDK now automatically migrates
device_id
,name
andmetadata
from versions before 7.0.0. After the user updates the app, those values stay the same, no additional steps required.
7.0.7
Fixed
- Added native methods to Proguard exceptions
- Reduced a chance of generating a null (all zeroes) device_id.
7.0.6
Fixed
- Sending unnecessary events to the server on
locate()
call when tracking is active. - Improve handling of invalid system location events.
7.0.5
Fixed
- In
location-services-google
,location-services-google-19-0-1
plugins: Not sending location and push token values
7.0.4
Fixed
- An intermittent crash on Samsung devices
- In
location-services-google
,location-services-google-19-0-1
plugins: A crash when using `locate()`` method when Google Location Services return null Location value