getUniqueId is not unique is some cases in iOS
See original GitHub issueHello,
Some of our users experienced an issue with the ID that we retrieved via getUniqueId()
: they have the same ID across two different devices.
We found a way to reproduce the problem: if a user uses the same Apple ID across two devices and has used iCloud to restore a backup from one device to another, getUniqueId
return the same string.
We are thinking about forking the library and removing the mechanism that saves and read from UserDefaults and Keychain. But before that, may I ask why this mechanism was implemented? Why not retrieve the ID always with the same mechanism using [[UIDevice currentDevice].identifierForVendor UUIDString];
?
PS: thanks for the lib, used it on several projects!
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
getUniqueId is not unique is some cases in iOS #519
Hello, Some of our users experienced an issue with the ID that we retrieved via getUniqueId(): they have the same ID across two...
Read more >How to get unique id of apple watch programatically?
Yes I think about generate UUID my self and save it in watch but in one case I need solution.If user change the...
Read more >How to get unique id in iOS device?
One easy solution to circumvent this is to use the Keychain to store the deviceId once acquired. If the keychain item is not...
Read more >Solved: Retrieving Unique ID Upon Record Creation
If you are using Form to submit the record, you can put Form1.LastSubmit.'Unique ID Field' to get Unique ID of new-created record.
Read more >Which is the best way to get unique id in iOS app?
There is no way to get a permanent unique ID. Before iOS7, we could get unique id with the help of Netwok card's...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
#538 should have an implementation more like #60 and thus not run into this. If you forked and implemented something like #60 or proposed a PR that did that, it could get us going in that direction
That proposed implementation would not survive app uninstall/reinstalls but I think an app that wants to do that might be better served with firebase or similar?
Hello 👋, this issue has been opened for more than 2 months with no activity on it. If the issue is sti ll here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solu tions and if you found one, please open a pull request! You have 7 days until this gets closed automatically