iOS开发 设计获取不变的UUID

获取UUID的方法有很多，但是都会因为各种原因改变

1. /** 卸载应用重新安装后会不一致*/

2. + (NSString *)getUUID{

3. CFUUIDRef uuid = CFUUIDCreate(NULL);

4. NSString *UUID = (__bridge_transfer NSString *)CFUUIDCreateString(NULL, uuid);

5. CFRelease(uuid);

6. return UUID;

7. }

8.  

9. /** 卸载应用重新安装后会不一致*/

10. + (NSString *)getUUID{

11. return [UIDevice currentDevice].identifierForVendor.UUIDString;;

12. }

13.  

14. /** 不会因为应用卸载改变

15. * 但是用户在设置-隐私-广告里面限制广告跟踪后会变成@"00000000-0000-0000-0000-000000000000"

16. * 重新打开后会变成另一个，还原广告标识符也会变

17. */

18. + (NSString *)getUUID{

19. return [[[ASIdentifierManager sharedManager] advertisingIdentifier] UUIDString];

20. }

作为设备唯一的标识符，一言不合就变了肯定是不行的呀

在产品汪的逼迫下，在我不懈的努力下，我终于找到一个可以一直保持一致的方法。第一次获取成功后保存到钥匙串，然后每次使用都通过钥匙串去拿。

第一步，打开应用的钥匙串权限

Target - Capabilities - KeychainSharing - ON

第二步，复制粘贴代码，懒得复制的可以去我的Github上直接下载

先粘.h文件

1. #import <Foundation/Foundation.h>

2.  

3. @interface KeyChainStore : NSObject

4. + (void)save:(NSString*)service data:(id)data;

5. + (id)load:(NSString*)service;

6. + (void)deleteKeyData:(NSString*)service;

7. @end

再粘.m文件

1. #import "KeyChainStore.h"

2.  

3. @implementation KeyChainStore

4.  

5. + (NSMutableDictionary*)getKeychainQuery:(NSString*)service {

6. return[NSMutableDictionary dictionaryWithObjectsAndKeys:

7. (id)kSecClassGenericPassword,(id)kSecClass,

8. service,(id)kSecAttrService,

9. service,(id)kSecAttrAccount,

10. (id)kSecAttrAccessibleAfterFirstUnlock,(id)kSecAttrAccessible,

11. nil];

12. }

13.  

14. + (void)save:(NSString*)service data:(id)data{

15. //Get search dictionary

16. NSMutableDictionary*keychainQuery = [self getKeychainQuery:service];

17. //Delete old item before add new item

18. SecItemDelete((CFDictionaryRef)keychainQuery);

19. //Add new object to searchdictionary(Attention:the data format)

20. [keychainQuery setObject:[NSKeyedArchiver archivedDataWithRootObject:data]forKey:(id)kSecValueData];

21. //Add item to keychain with the searchdictionary

22. SecItemAdd((CFDictionaryRef)keychainQuery,NULL);

23. }

24.  

25. + (id)load:(NSString*)service {

26. id ret =nil;

27. NSMutableDictionary*keychainQuery = [self getKeychainQuery:service];

28. //Configure the search setting

29. //Since in our simple case we areexpecting only a single attribute to be returned (the password) wecan set the attribute kSecReturnData to kCFBooleanTrue

30. [keychainQuery setObject:(id)kCFBooleanTrue forKey:(id)kSecReturnData];

31. [keychainQuery setObject:(id)kSecMatchLimitOne forKey:(id)kSecMatchLimit];

32. CFDataRef keyData =NULL;

33. if(SecItemCopyMatching((CFDictionaryRef)keychainQuery,(CFTypeRef*)&keyData) ==noErr){

34. @try{

35. ret =[NSKeyedUnarchiver unarchiveObjectWithData:(__bridge NSData*)keyData];

36. }@catch(NSException *e) {

37. NSLog(@"Unarchiveof %@ failed: %@",service, e);

38. }@finally{

39. }

40. }

41. if(keyData)

42. CFRelease(keyData);

43. return ret;

44. }

45.  

46. + (void)deleteKeyData:(NSString*)service {

47. NSMutableDictionary*keychainQuery = [self getKeychainQuery:service];

48. SecItemDelete((CFDictionaryRef)keychainQuery);

49. }

50.  

51. @end

第三步，使用(直接调这个方法就可以了)

1. /** 获取UUID*/

2. + (NSString *)getUUIDByKeyChain{

3. // 这个key的前缀最好是你的BundleID

4. NSString*strUUID = (NSString*)[KeyChainStore load:@"com.mycompany.myapp.usernamepassword"];

5. //首次执行该方法时，uuid为空

6. if([strUUID isEqualToString:@""]|| !strUUID)

7. {

8. // 获取UUID 这个是要引入<AdSupport/AdSupport.h>的

9. strUUID = [[[ASIdentifierManager sharedManager] advertisingIdentifier] UUIDString];

10.  

11. if(strUUID.length ==0 || [strUUID isEqualToString:@"00000000-0000-0000-0000-000000000000"])

12. {

13. //生成一个uuid的方法

14. CFUUIDRef uuidRef= CFUUIDCreate(kCFAllocatorDefault);

15. strUUID = (NSString*)CFBridgingRelease(CFUUIDCreateString(kCFAllocatorDefault,uuidRef));

16. CFRelease(uuidRef);

17. }

18.  

19. //将该uuid保存到keychain

20. [KeyChainStore save:@"com.mycompany.myapp.usernamepassword" data:strUUID];

21. }

22. return strUUID;

23. }

无论你怎么折腾都会保证同一设备每次获取到的UUID都是一致的，卸载应用，开启广告限制跟踪，系统升级都不会有影响。越狱刷机这种骚操作我没有测过，即使有问题，感觉这些调皮的用户也可以忽略了，因为这个已经是目前最好的解决办法了，如果大家有什么更好的解决方案，还请评论区指正。