New
v2.1.0
- library
- breaking changes
Fingerprinter.getFingerprintingSignalsProvider()returns a nullable type now. This is just a precaution measure though, and the likelihood of gettingnullfrom this method is super low. If you ever stumble upon such scenario, feel free to leave an issue. Also, this method has been annotated withWorkerThreadannotation, which is meant be a hint to avoid using this method on the main thread as it might take enough time to skip a few frames. - behavioural changes
- Previously, in case of some unexpected critical error in the library code, there was a chance that the callback passed to
Fingerprinter.getFingerprint()orFingerprinter.getDeviceId()methods would have never been fired. Now, this problem is resolved by returning some dummy result (currently, it's empty strings) and logging an error. As withFingerprinter.getFingerprintingSignalsProvider(), this is more of a precaution measure, and we don't expect the library users to ever face such scenario. But if you do, feel free to leave an issue ;)
- Previously, in case of some unexpected critical error in the library code, there was a chance that the callback passed to
- stability improvements As we were occasionally getting reports that some of the calls to the Android platforms APIs could never return on some devices, the timeout mechanism has been implemented. All the platform calls are safely wrapped now, so that none of such calls would be able to hang an entire library.
- breaking changes