Bot releases are hidden (Show)
Published by aws-mobile-appsync-sdk-ios-tools almost 4 years ago
Upgrade to 2.22.0 SDK. PR #451
Published by aws-mobile-appsync-sdk-ios-tools almost 4 years ago
Published by aws-mobile-appsync-sdk-ios-tools about 4 years ago
isCancelled
state. See Issue #342 and PR #355. Thanks, @LachlanMcCulloch!exponential
AWSAppSyncRetryStrategy when scheduling a delta sync when the appSyncClient reference is unavailable (#325).Breaking API Changes
Selection set filtering will be done per client as each client can define their own selection set. In this case the subscription selection set must be a subset of the mutation selection set. For example, a subscription addedPost{author title}
linked to the mutation addPost(...){id author title url version}
would receive only the author and the title of the post and none of the other fields. However, if the mutation didn't have the author in its selection set the subscriber would get a null
value for the author field (or an error in case the author field is defined as required/not-null in the schema).
In the earlier SDK version, if you didn’t configure the associated subscription selection set with the required fields and relied on the mutation fields to push data to subscribed client, the behavior will change when you move to this version that use pure WebSockets. In the example above, a subscription without the "author" field defined in its selection set would still return the author name with MQTT over WebSockets as the field is defined in the mutation, the same behavior won’t apply for pure WebSockets. The subscription selection set is essential when using pure WebSockets: if a field is not explicitly defined in the subscription it won't be returned by AWS AppSync.
Breaking Build Changes
AWSAppSyncSubscriptionError
AWSAppSyncClientError
AWSSQLLiteNormalizedCacheError
MutationCache
AWSAppSyncClientConfiguration
AWSAppSyncCacheConfiguration
Published by palpatim about 5 years ago
This release has invalid dependency declaration in the AWSAppSync.podspec. Please use release 2.14.3 instead.