iOS 获取设备唯一标示

http://blog.163.com/l1_jun/blog/static/1438638820155108054177/

原文链接:http://tinymission.com/post/ios-identifierforvendor-frequently-changing


When Apple got rid of access to the UDID for developers in Xcode 5.0, they promised a solution that would be unique for your company identifier and would be constant as long as at least one of your apps was installed on a device: identifierForVendor.

For the last month, I’ve been struggling with one of my enterprise distribution applications, where device identifiers have been changing frequently on many of my devices. It happens even when the app hasn’t been deleted, but it frequently occurs when the app version is upgraded, or even at random times. I track access and status by device, so having a reliable device identifier is essential for this project. I started receiving error notifications that device IDs didn’t exist in my database and began to monitor the situation more closely. I have now recorded several instances of a device ID changing during app usage, where I receive two notifications one minute or less apart containing two different device IDs. I can’t say for sure if this is unique to enterprise distributions, specific hardware types, specific OS versions, or something else, but I am definitely not imagining it. If you are a developer who needs a way to track access to your app by device, and you can’t control what OS your users are on, you need a better system. I’ve chosen to capture the identifierForVendor when the app is first installed and store it in the keychain. This has the advantage of persisting even when the app has been deleted, and can be used between apps as well. I came across a great Keychain wrapper calledUICKeyChainStore and put it into place. It’s a very simple library to implement and has worked great for my apps.

  1. Add Security.framework to your target
  2. Import the library using either Cocoapods or just adding the two relevant files to your project
  3. (Optional) Add the Keychain Sharing entitlement to your app target if you want the ability to share keychains between your different apps
  4. Store the device ID to the keychain:
    NSString *deviceId = [[UIDevice currentDevice] identifierForVendor] UUIDString];
    [UICKeyChainStore setString:deviceId forKey:@"deviceId" service:@"Devices"];
    
  5. Retrieve the device ID from the keychain:
    NSString *deviceId = [UICKeyChainStore stringForKey:@"deviceId" service:@"Devices"];

Updated for iCloud from one of our readers:
There is a risk of setting several device IDs the same if you back up this keychain entry to iCloud. This can happen in two ways:

  1. Through iCloud Keychain (meaning that the keychain would be synced to another one of my devices, and I’d get the same device identifier there as well)
  2. Through backups (the app’s data, including keychain, is saved on backups and can be restored to a new device, thus copying the device identifier)

For the item to be synced with iCloud keychain, I’d need to explicitly set the kSecAttrSynchronizableattribute, so that’s not happening.

Backups are indeed a potential problem, but I found out that you can add the attributekSecAttrAccessibleAlwaysThisDeviceOnly to prevent this.

Thanks for the feedback and additional input!


  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
提供的源码资源涵盖了Java应用等多个领域,每个领域都包含了丰富的实例和项目。这些源码都是基于各自平台的最新技术和标准编写,确保了在对应环境下能够无缝运行。同时,源码中配备了详细的注释和文档,帮助用户快速理解代码结构和实现逻辑。 适用人群: 适合毕业设计、课程设计作业。这些源码资源特别适合大学生群体。无论你是计算机相关专业的学生,还是对其他领域编程感兴趣的学生,这些资源都能为你提供宝贵的学习和实践机会。通过学习和运行这些源码,你可以掌握各平台开发的基础知识,提升编程能力和项目实战经验。 使用场景及目标: 在学习阶段,你可以利用这些源码资源进行课程实践、课外项目或毕业设计。通过分析和运行源码,你将深入了解各平台开发的技术细节和最佳实践,逐步培养起自己的项目开发和问题解决能力。此外,在求职或创业过程中,具备跨平台开发能力的大学生将更具竞争力。 其他说明: 为了确保源码资源的可运行性和易用性,特别注意了以下几点:首先,每份源码都提供了详细的运行环境和依赖说明,确保用户能够轻松搭建起开发环境;其次,源码中的注释和文档都非常完善,方便用户快速上手和理解代码;最后,我会定期更新这些源码资源,以适应各平台技术的最新发展和市场需求。 所有源码均经过严格测试,可以直接运行,可以放心下载使用。有任何使用问题欢迎随时与博主沟通,第一时间进行解答!

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值