The issue is that many libraries still used this function to uniquely identify devices for analytics (e.g. content-based advertising?) or for legitimate functio

The issue is that many libraries still used this function to uniquely identify devices for analytics (e.g. content-based advertising?) or for legitimate functionality (TestFlight, cross app communication). Many people might drag-and-drop a library into their app, it all works, and then suddenly their next update is now rejected and it wasn't "their fault". Some, as on stackoverflow, don't even know where to begin to address the issue.