You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a lot of deprecations and warnings in SyncKit, could you update the library with the most common things? I have summarized them in a list instead of overwriting this git library.
A recent iOS version stats counter from Apple showing that there are only 11% devices which are still having iOS 9 (9%) or earlier (2%), and 89% of devices have IOS 10. I believe you should drop out support for those versions or if you want to support IOS 9, it should be better a version check, but don't use basically deprecated codes. Watch OS 4 will available at all Watch series, so it is simply not worth supporting older versions than WatchOS 3.0.
1. Nullability Issues in Obj-C - nonnul and nullable QSChangeManager.h file mostly 2. Deprecations:
suggestion: if #available(iOS 9, *) {}
for:
CKOwnerDefaultName in QSCloudKitSynchronizer+CoreData.m - row 43
I have a lot of deprecations and warnings in SyncKit, could you update the library with the most common things? I have summarized them in a list instead of overwriting this git library.
A recent iOS version stats counter from Apple showing that there are only 11% devices which are still having iOS 9 (9%) or earlier (2%), and 89% of devices have IOS 10. I believe you should drop out support for those versions or if you want to support IOS 9, it should be better a version check, but don't use basically deprecated codes. Watch OS 4 will available at all Watch series, so it is simply not worth supporting older versions than WatchOS 3.0.
1. Nullability Issues in Obj-C - nonnul and nullable QSChangeManager.h file mostly
2. Deprecations:
suggestion:
if #available(iOS 9, *) {}
for:
CKOwnerDefaultName
in QSCloudKitSynchronizer+CoreData.m - row 43CKFetchRecordChangesOperation
in QSCloudKitSynchronizer.m - row 494 and 565one more in QSManagedObjectContext.m
The text was updated successfully, but these errors were encountered: