我也遇到了一些问题，解决方法很简单:

    // Get Bundle Info for Remote Registration (handy if you have more than one app)
    NSString *appName = [[[NSBundle mainBundle] infoDictionary] objectForKey:@"CFBundleDisplayName"];
    NSString *appVersion = [[[NSBundle mainBundle] infoDictionary] objectForKey:@"CFBundleVersion"];


    // Get the users Device Model, Display Name, Unique ID, Token & Version Number
    UIDevice *dev = [UIDevice currentDevice];
    NSString *deviceUuid=[dev.identifierForVendor  UUIDString];

    NSString *deviceName = dev.name;

不要使用这些库——libOmnitureAppMeasurement，它使用了苹果不再支持的uniqueIdentifier

您可能想要考虑使用OpenUDID，它是已弃用UDID的临时替代品。

基本上，要匹配UDID，需要以下特性:

唯一的或足够唯一的(低概率碰撞是 可能是可以接受的) 跨重启、恢复、卸载的持久性 在不同供应商的应用程序中可用(通过CPI网络获取用户很有用)-

OpenUDID实现了上述功能，甚至有一个内置的选择退出机制供以后考虑。

检查http://OpenUDID.org，它指向相应的GitHub。 希望这能有所帮助!

作为旁注，我将回避任何MAC地址的替代方案。虽然MAC地址似乎是一种诱人的通用解决方案，但要确保这个唾手可得的果实是有毒的。MAC地址是非常敏感的，在你说“提交这个应用程序”之前，苹果可能会非常反对访问这个地址……MAC网络地址用于对wlan (private lan)或其他vpn (virtual private network)中的某些设备进行认证。它甚至比以前的UDID更敏感!

使用上面提到的SSKeychain和代码。下面是复制/粘贴(添加SSKeychain模块)的代码:

+(NSString *) getUUID {

//Use the bundle name as the App identifier. No need to get the localized version.

NSString *Appname = [[[NSBundle mainBundle] infoDictionary] objectForKey:@"CFBundleName"];    

//Check if we have UUID already

NSString *retrieveuuid = [SSKeychain passwordForService:Appname account:@"user"];

if (retrieveuuid == NULL)
{

    //Create new key for this app/device

    CFUUIDRef newUniqueId = CFUUIDCreate(kCFAllocatorDefault);

    retrieveuuid = (__bridge_transfer NSString*)CFUUIDCreateString(kCFAllocatorDefault, newUniqueId);

    CFRelease(newUniqueId);

    //Save key to Keychain
    [SSKeychain setPassword:retrieveuuid forService:Appname account:@"user"];
}

return retrieveuuid;

}

也许你可以用:

[UIDevice currentDevice].identifierForVendor.UUIDString

苹果的文档对identifierforvendor的描述如下:

对于运行在同一设备上的来自同一供应商的应用程序，此属性的值是相同的。对于同一设备上来自不同供应商的应用程序，以及不同设备上的应用程序，无论供应商如何，都会返回不同的值。

我相信苹果公司的这一变化惹恼了很多人。我开发了一个iOS的簿记应用程序，并有一个在线服务来同步不同设备上的更改。该服务维护所有设备的数据库以及需要传播到这些设备的更改。因此，了解哪种设备是哪种设备很重要。我使用UIDevice uniqueIdentifier跟踪设备，为了它的价值，这里是我的想法。

Generate a UUID and store in user defaults? No good because this does not persist when the user deletes the app. If they install again later the online service should not create a new device record, that would waste resources on the server and give a list of devices containing the same one two or more times. Users would see more than one "Bob's iPhone" listed if they re-installed the app. Generate a UUID and store in the keychain? This was my plan, since it persists even when the app is uninstalled. But when restoring an iTunes backup to a new iOS device, the keychain is transferred if the backup is encrypted. This could lead to two devices containing the same device id if the old and new devices are both in service. These should be listed as two devices in the online service, even if the device name is the same. Generate a hash the MAC address and bundle id? This looks like the best solution for what I need. By hashing with the bundle id, the generated device id is not going to enable the device to be tracked across apps and I get a unique ID for the app+device combination.

有趣的是，苹果自己的文档提到通过计算系统Mac地址加上bundle id和版本的哈希来验证Mac App Store收据。所以这似乎是政策允许的，但是否通过应用审查我还不知道。