Apple really condemned the UDID because of third-party companies that exist to aggregate (as with payment) data from application developers to sell ads.
See cookie tracking, same concept. Thus, while technically justified and huge convenience for developers who do not want to require a username and password for their applications, because of third-party tracker companies, this is disastrous for user privacy.
Apple now supports the UUID (Universal Unique Identifier), which can be extracted from the SDK, which uniquely identifies this user for the application itself, but not for all applications.
This isolates the identifier, does not require the developer to resort to hacks, such as the MAC address, and protects the user from third-party tracking schemes.
If you are not using a UUID, expect Apple to reject your application. Even if you use a Mac address, you do not necessarily avoid detection, as there are almost no reasons why the application will require such information to work.
bobx Jun 05 2018-12-12T00: 00Z
source share