Rajesh-Royal/Broprint.js

Bug: Same fingerprint to user that use iPhone

juanurcola opened this issue · 11 comments

juanurcola commented

I could to see that users who have iphone, always generate the same fingerprint

5950378396046291

I tested in differente iphones and browsers (safari and chrome)

Step to reproduce

  1. Go to the website https://broprintjs.netlify.app/ from a iphone (using chrome o safari)
  2. Click on Generate FingerPrint Button
geekhunger commented

I could to see that users who have iphone, always generate the same fingerprint

5950378396046291

I tested in differente iphones and browsers (safari and chrome)

Step to reproduce

  1. Go to the website https://broprintjs.netlify.app/ from a iphone (using chrome o safari)
  2. Click on Generate FingerPrint Button

My iPhones received the exact same fingerprint as yours! Very interesting find!

At first, I didn't notice that my ID was the same as yours and I was thinking it's because of my iPhones going through the same network. Must be a bug then, I guess (or Safari has implemented new defense methods against fingerprinting with Canvas/Audio).

  • 👍1
larinius commented

Chrome, Edge - same issue
image

  • 👍1
abhishek77in commented

Oh! I thought this was a really promising library.

  • 😕5
abhishek77in commented

Is this is a real issue, this point (this post) should be highlighted in the REAME instead of saying this library is only for educational purposes.

  • 👍1
paulvl commented

Even fingerprintjs pro have issues with Edge, you cant test it https://fingerprint.com/demo/

claysam75 commented

I also see exactly the same fingerprint when using an iphone. Such a shame, I would have replaced fingerprintjs with this in a heartbeat otherwise.

  • 😕4
anelad commented

Yep, same here, at least for my iPhone. My girlfriends' iPhone gives a different one tho

Rajesh-Royal commented

Not sure what is the actual issue, but I was thinking of implementing a tracking option to track unique users by their IP address using ipify. But again It can have less accuracy if the user started using a VPN.

If anyone has any suggestions or ideas please share.

jalsco commented

So it isn't working... 😢
Such a shame - I wanted to use this library ! It looks perfect, and also easy to implement.
But requirement, obviously, is that each Visitor device gets a unique I

Rajesh-Royal commented

No fix available as of now, open to accept PR.

jalsco commented

ok - hopefully the library can be improved at a later date. All respect to you ! 🙏🏻 I will keep a watch on this project, so much promise here, and is already so very close !

Like many, my needs are to (within statistical reasonableness) detect UNIQUE device/browser visitors. So at this time this library cannot be used for that. Thanks for replying 🙏🏻