Hi Nic, the problem is persistence. Any time the user deletes the app and then re-installs the app, you'd get a new GUID as an ID. So what you can do is create a UIPasteboard with persistence set to true, and if named differently from the app, tends to persist beyond the lifetime of the app. I say tends to, as it is still possible to be deleted, so OpenUDID tries to get around this by creating a range of pasteboards (in this case 100), that are used by it and other apps that support OpenUDID, so that it becomes less likely that the unique ID is deleted.
Here's a good article on OpenUDID and other schemes: http://www.infosecisland.com/blogview/21207-A-Field-Guide-to-Post-UDID-Unique-IDs-on-iOS.html Dennis -- View this message in context: http://monotouch.2284126.n4.nabble.com/Monotouch-port-of-OpenUDID-tp4644130p4644656.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list MonoTouch@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monotouch
