Treasure Data has released the Treasure Data iOS SDK v0.6.0 which removes usage of MD5 functions as recommended by Apple for iOS SDK 13.0.
There is no deadline to upgrade and no fixed date from Apple for these functions to be completely removed. An upgrade to the latest TD iOS SDK is recommended.
- Beginning with iOS SDK 13.0 and later, Apple has officially deprecated MD5 hashing functions usage in CommonCrypto API. You may receive the following warning message:
These functions are cryptographically broken and should not be used in security contexts.Clients should migrate to SHA256 (or stronger).
Reference http://codeworkshop.net/objc-diff/sdkdiffs/ios/13.0/CommonCrypto.md
TD iOS SDK uses some of these functions to generate projectID which is used internally for storage tables and other functions. The new SDKv0.6.0 uses a stronger hashing function and removes the warning message from iOS SDK 13.0.
As a result of the above change, applications with TD iOS SDK v0.6.0 cannot access local storage created by TD iOS SDK v0.5.0 or earlier. This means that data generated by the older version may not be uploaded to your Treasure Data account.
- All customers who are using TD iOS SDK v0.5.0 or earlier
There is no immediate action required. However, application developers using TD iOS SDK can take some steps in preparation before using the new SDK version:
If data/event in the cache is being uploaded to Treasure Data by calling
uploadEvent()function frequently and regularly, for example, when the application is closing and the cache is clear, no further action necessary.If data/event in the cache does not get uploaded frequently, the developer must ensure the cache is clear before migrating to 0.6.0 by calling
uploadEvent()function frequently to minimize data loss.
- There is no due date. Apple is yet to officially announce when the deprecated functions in CommonCrypto APIs will be removed.