獲取UUID的方法有很多,但是都會因爲各種原因改變
/** 卸載應用重新安裝後會不一致*/
+ (NSString *)getUUID{
CFUUIDRef uuid = CFUUIDCreate(NULL);
NSString *UUID = (__bridge_transfer NSString *)CFUUIDCreateString(NULL, uuid);
CFRelease(uuid);
return UUID;
}
/** 卸載應用重新安裝後會不一致*/
+ (NSString *)getUUID{
return [UIDevice currentDevice].identifierForVendor.UUIDString;;
}
/** 不會因爲應用卸載改變
* 但是用戶在設置-隱私-廣告裏面限制廣告跟蹤後會變成@"00000000-0000-0000-0000-000000000000"
* 重新打開後會變成另一個,還原廣告標識符也會變
*/
+ (NSString *)getUUID{
return [[[ASIdentifierManager sharedManager] advertisingIdentifier] UUIDString];
}
作爲設備唯一的標識符,一言不合就變了肯定是不行的呀
在產品汪的逼迫下,在我不懈的努力下,我終於找到一個可以一直保持一致的方法。第一次獲取成功後保存到鑰匙串,然後每次使用都通過鑰匙串去拿。
第一步,打開應用的鑰匙串權限
Target - Capabilities - KeychainSharing - ON
添加 com.mycompany.myapp.usernamepassword(這個key隨便設置)
第二步,複製粘貼代碼,
先粘.h文件
#import <Foundation/Foundation.h>
@interface KeyChainStore : NSObject
+ (void)save:(NSString*)service data:(id)data;
+ (id)load:(NSString*)service;
+ (void)deleteKeyData:(NSString*)service;
@end
再粘.m文件
#import "KeyChainStore.h"
@implementation KeyChainStore
+ (NSMutableDictionary*)getKeychainQuery:(NSString*)service {
return[NSMutableDictionary dictionaryWithObjectsAndKeys:
(id)kSecClassGenericPassword,(id)kSecClass,
service,(id)kSecAttrService,
service,(id)kSecAttrAccount,
(id)kSecAttrAccessibleAfterFirstUnlock,(id)kSecAttrAccessible,
nil];
}
+ (void)save:(NSString*)service data:(id)data{
//Get search dictionary
NSMutableDictionary*keychainQuery = [self getKeychainQuery:service];
//Delete old item before add new item
SecItemDelete((CFDictionaryRef)keychainQuery);
//Add new object to searchdictionary(Attention:the data format)
[keychainQuery setObject:[NSKeyedArchiver archivedDataWithRootObject:data]forKey:(id)kSecValueData];
//Add item to keychain with the searchdictionary
SecItemAdd((CFDictionaryRef)keychainQuery,NULL);
}
+ (id)load:(NSString*)service {
id ret =nil;
NSMutableDictionary*keychainQuery = [self getKeychainQuery:service];
//Configure the search setting
//Since in our simple case we areexpecting only a single attribute to be returned (the password) wecan set the attribute kSecReturnData to kCFBooleanTrue
[keychainQuery setObject:(id)kCFBooleanTrue forKey:(id)kSecReturnData];
[keychainQuery setObject:(id)kSecMatchLimitOne forKey:(id)kSecMatchLimit];
CFDataRef keyData =NULL;
if(SecItemCopyMatching((CFDictionaryRef)keychainQuery,(CFTypeRef*)&keyData) ==noErr){
@try{
ret =[NSKeyedUnarchiver unarchiveObjectWithData:(__bridge NSData*)keyData];
}@catch(NSException *e) {
NSLog(@"Unarchiveof %@ failed: %@",service, e);
}@finally{
}
}
if(keyData)
CFRelease(keyData);
return ret;
}
+ (void)deleteKeyData:(NSString*)service {
NSMutableDictionary*keychainQuery = [self getKeychainQuery:service];
SecItemDelete((CFDictionaryRef)keychainQuery);
}
@end
第三步,使用(直接調這個方法就可以了)
/** 獲取UUID*/
+ (NSString *)getUUIDByKeyChain{
// 這個key的前綴最好是你的BundleID
NSString*strUUID = (NSString*)[KeyChainStore load:@"com.mycompany.myapp.usernamepassword"];
//首次執行該方法時,uuid爲空
if([strUUID isEqualToString:@""]|| !strUUID)
{
// 獲取UUID 這個是要引入<AdSupport/AdSupport.h>的
strUUID = [[[ASIdentifierManager sharedManager] advertisingIdentifier] UUIDString];
if(strUUID.length ==0 || [strUUID isEqualToString:@"00000000-0000-0000-0000-000000000000"])
{
//生成一個uuid的方法
CFUUIDRef uuidRef= CFUUIDCreate(kCFAllocatorDefault);
strUUID = (NSString*)CFBridgingRelease(CFUUIDCreateString(kCFAllocatorDefault,uuidRef));
CFRelease(uuidRef);
}
//將該uuid保存到keychain
[KeyChainStore save:@"com.mycompany.myapp.usernamepassword" data:strUUID];
}
return strUUID;
}
swfit 版本:
func getUUIDByKeyChain() -> String {
var strUUID = KeyChainStore.load("com.mycompany.myapp.usernamepassword") as? String
if strUUID == Optional<String>.none {
strUUID = ASIdentifierManager.shared().advertisingIdentifier.uuidString
if (strUUID as AnyObject).count == 0 || strUUID == "00000000-0000-0000-0000-000000000000" {
var uuidRef = CFUUIDCreate(kCFAllocatorDefault)
strUUID = (CFBridgingRetain(CFUUIDCreateString(kCFAllocatorDefault, uuidRef)) as! String)
uuidRef = nil
}
KeyChainStore.save("com.mycompany.myapp.usernamepassword", data: strUUID as Any)
}
return strUUID!
}
無論你怎麼折騰都會保證同一設備每次獲取到的UUID都是一致的,卸載應用,開啓廣告限制跟蹤,系統升級都不會有影響。越獄刷機這種騷操作我沒有測過,即使有問題,感覺這些調皮的用戶也可以忽略了,因爲這個已經是目前最好的解決辦法了,如果大家有什麼更好的解決方案,還請評論區指正。