fingerprintjs / fingerprintjs-android

Swiss army knife for identifying and fingerprinting Android devices. MIT license, no restrictions on usage in production.
https://fingerprint.com/github/
MIT License
572 stars 83 forks source link

Caussed by: android.system.ErrnoException - statvfs failed: ENOENT (No such file or directory) #90

Closed puzanshrestha closed 1 year ago

puzanshrestha commented 1 year ago

Crashes on Samsung devices Samsung Galaxy S23 Ultra Android 13

libcore.io.Linux.statvfs (Linux.java)
libcore.io.ForwardingOs.statvfs (ForwardingOs.java:852)
libcore.io.BlockGuardOs.statvfs (BlockGuardOs.java:428)
libcore.io.ForwardingOs.statvfs (ForwardingOs.java:852)
android.system.Os.statvfs (Os.java:909)
android.os.StatFs.doStat (StatFs.java:51)
android.os.StatFs.<init> (StatFs.java:43)
com.fingerprintjs.android.fingerprint.FingerprinterFactory.createMemoryInfoProvider (FingerprinterFactory.kt:145)
com.fingerprintjs.android.fingerprint.FingerprinterFactory.createHardwareSignalGroupProvider (FingerprinterFactory.kt:92)
com.fingerprintjs.android.fingerprint.FingerprinterFactory.initializeFingerprinter (FingerprinterFactory.kt:79)
com.fingerprintjs.android.fingerprint.FingerprinterFactory.getInstance (FingerprinterFactory.kt:63)
Sergey-Makarov commented 1 year ago

Hey! Thanks for your report!

First of all, could you please tell which version of the library you are using? Judging by the stacktrace provided, the version is something below 1.2.1, which is quite old. So I would suggest you to update to the latest version, which is 2.0.1 at the moment, and check whether the issue still remains. We had a PR that was merged into 1.2.1 that can potentially address exactly this issue, so it's definitely worth trying :)

puzanshrestha commented 1 year ago

Hey! Thanks for your report!

First of all, could you please tell which version of the library you are using? Judging by the stacktrace provided, the version is something below 1.2.1, which is quite old. So I would suggest you to update to the latest version, which is 2.0.1 at the moment, and check whether the issue still remains. We had a PR that was merged into 1.2.1 that can potentially address exactly this issue, so it's definitely worth trying :)

Thanks @Sergey-Makarov. Yes I have been using older version 1.1, will update to the latest version.

Sergey-Makarov commented 1 year ago

Hey! Closing the issue for now, feel free to reopen it if the problem still exists.