iOS learning-unique identifiers

<span id="Label3"></p><strong><strong>1. Apple Advertising audit rules</strong></strong> <br> <br>If your app collects idfa, but it's not used when it's on the shelves, it's definitely rejected.<br> <br>If your app collects idfa, but does not use the AD service when it is definitely rejected, this time if integrated ads will not be affected<br> <br> <br> <strong><strong>2. How to avoid Apple ads</strong></strong> <br> <br>IDFA is able to identify users more precisely, especially for advertisers to track the conversion rate of ads to provide a great help. The Friend League statistical Analysis SDK collects IDFA to ensure that when Apple changes a unique identifier (for example, from Udid to openudid), the user data is steadily transitioning without data bursting.<br> <br>If your app is AppStore rejected due to IDFA issues, you can take the following advice:<br>1. Try the appeal as the advertiser, The Advertiser collects the IDFA logo is allowed;<br>2. Integrate any advertising service, choose to continue to use or close the service after going online;<br>3. Change the Apple account to resubmit the app (the developer has passed the review successfully).<br>4. No acquisition of IDFA means that the opportunity to accurately track users is abandoned, and there is a risk in ensuring the stability and consistency of the Data. If you still want to not collect idfa, you can download the SDK without IDFA version here<br> <br> <strong><strong>3. Unique serial number of Apple history version</strong></strong> <br> <br> <strong><strong>Cfuuid</strong></strong> <br>IOS2.0 began to exist, it is part of the Corefoundatio package, so the API belongs to C language style<br>The system is not stored for this cfuuid Value. Each time you call cfuuidcreate, the system returns a new unique identifier<br> <br> <strong><strong>Nsuuid</strong></strong> <br>IOS 6 only appears, which is almost exactly the same as cfuuid, except that it is the Objective-c interface<br>Like cfuuid, This value system is not stored, and a new unique identifier is obtained each time it is Called.<br>It's different every time you run it, but the only thing That's generated is<br> <br> <strong><strong>IDFA (idfa-identifierforidentifier)</strong></strong> <br>New methods appear in IOS 6, Advertisingidentifier is a part of the new framework adsupport.framework the ad identifier is stored by the System. however, even though this is stored by the system, there are several cases where the ad identifier is Regenerated. This ad identifier is regenerated if the user completely resets the system (restore location and privacy, general-purpose, setup, and so on). In addition, if the user explicitly restores the ads (set-up, general-purpose, and so on, to the ads, and restore the ad identifiers), then the ad identifiers will be Regenerated. With respect to the restoration of the ad identifier, it is important to note that if the program is running in the background, the user "restores the ad identifier" and then goes back to the program, and then gets the ad identifier and does not immediately get the restored Identifier. You must terminate the program before restarting the program to obtain the restored AD Identifier. I guess this is because Asidentifiermanager is a single case.<br> <br> <strong><strong>Vindor ((idfv-identifierforvendor)</strong></strong> <br>New methods appear in IOS 6, but the new method of getting this IDFV is added to the existing Uidevice class.<br>As with advertisingidentifier, This method returns a Nsuuid Object.<br>NSString *IDFV = [[[uidevice currentdevice] identifierforvendor] uuidstring];<br>The "he value" is the "same for apps" come from the same vendor running on the same device. A different value is returned for apps on the same device this come from different vendors, and to apps on different Devi Ces regardless of vendor.<br>If such a condition is met, then the property value obtained will not change: the same vindor-same device, IDFV the Same. If this is the case, then the value will not be the same: the same device-different vindor, or different devices-whether or not the same vindor.<br>Vendor is very simple: a vendor is the first two parts of the Cfbundleidentifier (reverse DNS format). For example, Com.doubleencore.app1 and com.doubleencore.app2 get the same Identifierforvendor because the first two parts of their cfbundleidentifier are the Same. But the Identifierforvendor is completely different: com.massivelyoverrated or Net.doubleencore. One thing to note here is that if the user uninstalls all the programs for the same vendor and then re-installs the program provided by the same vendor, Identifierforvendor will be reset at this Point.<br>Vendor is the first two parts of Cfbundleidentifier (reverse DNS format). Applications from the same carrier run on the same device, the value of this property is the same, and different carrier applications run on the same device with different values.<br> <br> <strong><strong>UDID</strong></strong> <br>iOS5 has been abandoned, the System's unique serial number, app account added is the use of this<br> <br> <strong><strong>Openudid</strong></strong> <br>The Openudid on each device is generated by the first app with the Openudid SDK package, of course, if the machine is re-brushed this will still be lost<br>When iOS 5 was released, uniqueidentifier was deprecated, causing the vast majority of developers to look for a solution that would replace Udid and not be controlled by apple. This openudid became the most widely used open source Udid Alternative. Openudid is easy to implement in engineering and supports a range of advertising Providers.<br>NSString *openudid = [openudid value];<br>Openudid has used a very ingenious method of storing identifiers between different PROGRAMS-A special name used to store identifiers in the Pasteboard. In this way, other programs (also using Openudid) know where to go to get the identifiers that have been generated (instead of generating a new one).<br>As already mentioned, in the future, Apple will start forcing the use of advertisingidentifier or Identifierforvendor. If this day comes, even Openudid looks like a very good choice, but you may have to transition to Apple's approach<br> <br> <strong><strong>MAC address</strong></strong> <br>The MAC address is just like the ID number on our ID card, which is globally Unique. This makes it very good to identify the device uniqueness, similar to the udid number of the Apple device, from IOS7 and later, if you request a MAC address from your iOS device, the system will return a fixed value of "02:00:00:00:00:00"<span class="current prev"><span class="current prev">Prev<span class="current">1<span class="current next">Next</span> </span> </span></span><span class="pipe"><span class="pipe"><br></span></span><span class="ui-btn-inner"><span class="ui-btn-inner"><span class="ui-icon ui-icon-back ui-icon-shadow"> </span></span></span><p><p>iOS learning-unique identifiers</p></p></span>