v2.2.0

Breaking changes

• Kotlinx-serialization library has been removed in favor of Android's built in org.json library.
• All methods which received JsonObject now receive org.json.JSONObject

v2.1.2

Bug Fix

• onDestroy() method of the Naurt object could cause consistent warnings of Android catching exceptions on some phones. This has now been fixed.

v2.1.1

Change Log

• Internal bug fixes.

v2.1.0

Breaking changes

• Dependency added. implementation 'com.google.android.gms:play-services-location:21.0.1' is now required to successfully build an run Naurt. This is no used as the default pass through when Naurt is not validated to ensure locations are always available.
• UI update. Analytics sessions have been removed in favour of a simplified UI using the method "updateMetadata".

Change log

• Naurt precision and accuracy improved.
• Stability improved

v2.0.8

Change log

Battery optimisation

• New battery optimisation option added "activateBatteryOptimisation" will activate Naurt's battery saving mode. This will disable some features such as indoor/outdoor flags when at high speeds or stationary for long periods of time.
• Choose Naurt Location frequency New API added to throttle Naurt outputs

Features

• New event "NaurtLocationEnabledEvent" will return a boolean providing information on whether the user has turned off or on their location.

v2.0.7

Change Log

• Proguard rules now included in aar. Rules should be automatically applied when using the Naurt SDK.
• Small commons compress fix. Way in which the SDK interacts with the compress library changed. Crashes on some devices mitigated.

v2.0.6

Change Log

• Small battery optimizations.

v2.0.5

Change Log

• Behavior change in the way missing proguard rules are handled. Please check the relevant sections in the documentation.

v2.0.4

Bug fixes

• Small internal bug fixes. Slight improvement in performance.

v2.0.3

Change Log

• Naurt API keys can be configured to upload 0 data. This should be discussed with the sales team and used for sensitive use cases.
• Better detect when battery optimisation is affecting tracking performance.