AWS AppSync SDK for iOS - CHANGELOG

The AWS AppSync SDK for iOS enables you to access your AWS AppSync backend and perform operations like Queries, Mutations and Subscriptions. The SDK also includes support for offline operations.

3.6.0

Features

• feat: Upgrade AppSyncRTClient 1.8.0 and enable logs (PR #519)

Bug Fixes

• fix: Thread safe subscription watcher cancel (PR #523)

3.5.0

Misc. Updates

• feat: Upgrade AppSyncRealTimeClient 1.7.0 for Starscream 4 (PR #518)
• AppSync SDK is now also released as an XCFramework (PR #521)

3.4.3

• AppSync is now built with Xcode 13.2 in the CI/CD pipeline
• Upgrade to 2.27.0 SDK. PR #514

3.4.2

• AppSync is now built with Xcode 13.1 and Swift 5.5 in the CI/CD pipeline
• Fixed race condition on activeTimer access in AWSAppSyncHTTPNetworkTransport

3.4.1

Misc. Updates

• Update to 2.26.0 SDK dependencies (PR #492)

3.4.0

Misc. Updates

• Updated LambdaAuthInterceptor to support async auth provider (PR #488)

3.3.1

Misc. Updates

• Update to 2.25.0 SDK dependencies (PR #484)

3.3.0

New Features

• Added support for AWS Lambda auth mode (PR #478)

3.2.1

Misc. Updates

• Update to 2.24.0 SDK dependencies (PR #472)

3.2.0

New Features

• Swift Package Manager
  • The AWS AppSync SDK for iOS can now be installed via Swift Package Manager. See the README for full details.

Misc. Updates

• Update dependencies (PR #467)

3.1.17

Misc. Updates

• Update dependencies (PR #462)

3.1.16

Misc. Updates

• chore: Pinned Reachability library version to 5.0.0 (PR #455)

3.1.15

Misc. Updates

• Update dependencies to consume AppSyncRealTimeClient fix for race condition on disconnect (PR #454)

3.1.14

Misc. Updates

• Update dependencies (PR #451)

3.1.13

Misc. Updates

• Update dependencies. (PR #445)

3.1.12

Misc. Updates

• Add a parameter for the api key expiration for integ test setup CFN template (PR #439)
• Update dependencies. (PR #441)

3.1.11

Misc. Updates

• Refactored AWSAppSyncHTTPNetworkTransport to simplify internal auth handling, and to support providing your own URLSession in the new initializer. (PR #422). Thanks for the initial PR, @lesmuc! 🎉
• Update dependencies. (PR #436)

3.1.10

Misc. Updates

• Update dependencies. (PR #432)

3.1.9

Misc. Updates

• Fix Carthage build PR #423
• Support Xcode 12 PR #419
• Fix dependency version in podspec PR #428

3.1.8

Deprecated release

This release is deprecated due to errors. Please use 3.1.9 or greater.

3.1.7

Deprecated release

This release is deprecated due to errors. Please use 3.1.8 or greater.

3.1.6

Misc. Updates

• Upgrade to 2.16.0 SDK. PR #410

3.1.5

Bug Fixes

• Fix bug in subscription where data is not translated correctly to a format valid for JSONSerialization (See Issue #401, PR #402). Thanks @LachlanMcCulloch! 🎉

Misc. Updates

• Updated to latest dependencies
• AppSync is now built with Xcode 11.6 in the CI/CD pipeline

3.1.4

Bug Fixes

• Updated AppSync RealTime Client, which fixes stale connection handling upon resume from background:
  • #396
  • #403
  • Also see aws-amplify/aws-appsync-realtime-client-ios#24

Misc. Updates

• Updated to latest dependencies

3.1.3

General SDK improvements

• Upgrade to 2.14.0 SDK and 1.2.0 realtime client. See PR #400

Misc. Updates

• Changed the repo's default branch to 'main'
• Build Carthage binaries using Xcode 11.5

3.1.2

General SDK improvements

• Upgrade to AppSyncRealTimeClient 1.1.6

Misc. Updates

• Fix SwiftLint violation (PR #379) Thanks @RafaelPlantard!
• Update AWS dependencies to 2.13.1
• Add SwiftLint as a Pod dependency

3.1.1

Deprecated release

This release is deprecated due to errors. Please use 3.1.2 or greater.

3.1.0

General SDK improvements

• Add Codable and Hashable to AWSAppSyncAuthType. See PR #352 Thanks @LachlanMcCulloch!
• Improved AppSyncSubscriptionWithSync with fixing retain cycle and adding isCancelled state. See Issue #342 and PR #355. Thanks, @LachlanMcCulloch!
• Use AppSyncRealTimeClient 1.1.0 containing consolidated interceptors. See PR #353 for more details
• Update to use AppSyncRealTimeClient ~> 1.1, with Cartfile fix. See PR #367

3.0.2

Bug Fixes

• Default to exponential AWSAppSyncRetryStrategy when scheduling a delta sync when the appSyncClient reference is unavailable (#325).
• Remove force-unwrap in derivation of retry strategy during delta sync. See issue #325 PR #327.
• Fix strong reference cycle in delta sync. See issue #342 PR #343. Thanks, @LachlanMcCulloch!

Misc. Updates

• Moved Realtime subscription connection logic to a separate package. See PR #338
• Made internal subscription connection to receive null as data in variables.
• Updated podspec file to use the right source file.

3.0.1

Deprecated release

This release is deprecated due to errors. Please use 3.0.2 or greater.

3.0.0

General SDK improvements

• Breaking API Changes

  • Added support for connecting to AWS AppSync using pure WebSockets for GraphQL subscriptions.

    • 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

  • Adopted Semantic versioning
    • Starting with version 3.0.0 AppSync AWS iOS SDK will follow semantic versioning.

Misc. Updates

• Updated Reachability dependency to 5.0.0

2.15.0

Misc. Updates

• General SDK improvements
  • Breaking Build Change Removed deprecated APIs for
    • AWSAppSyncSubscriptionError
    • AWSAppSyncClientError
    • AWSSQLLiteNormalizedCacheError
    • MutationCache
    • AWSAppSyncClientConfiguration
    • AWSAppSyncCacheConfiguration
  • Breaking Build Change The AWS AppSync SDK for iOS now requires Xcode 11 or above to build
  • AppSync is now built targeting Swift 5.1
• Updated AWS SDK dependencies to 2.12.0
• Updated Reachability dependency to 4.3.1
• Updated SQLite.Swift dependency to 0.12.2

2.14.3

Bug Fixes

• Fixed a bug where data less than 128 bytes would cause a crash if logging were enabled. See issues #258 and #216, and PR #259. Thanks @johnmurphy01! 🎉

Misc. Updates

• Updated AWS SDK dependencies to 2.11.0

2.14.2

Deprecated Release

This release has invalid dependency declaration in the AWSAppSync.podspec. Please use release 2.14.3 instead.

2.14.1

Misc. Updates

• Updated AWS SDK dependencies to 2.10.2

2.14.0

Bug Fixes

• Fix a bug where delta sync was not correctly storing/ retrieving the lastSyncTime. See issue #232
• Breaking API Change To fix the delta sync logic, there was a change in the hashing function used internally. This change can cause the existing app to ignore the cache for the first sync and fetch data using base query. Subsequent sync operation should work as normal.

2.13.1

Bug Fixes

• Fixed a bug where calling multiple subscriptions in a burst could result in a crash.

2.13.0

New Features

• Support multiple authorization modes for a single AWS AppSync GraphQL endpoint.

• Breaking API Change Introduced clientDatabasePrefix in the AWSAppSyncServiceConfigProvider that accepts a prefix that will be used in the construction of database name for caching query responses, offline mutations and subscriptions metadata. The usage of the prefix can be enabled by the flag useClientDatabasePrefix: true as part of the AWSAppSyncCacheConfiguration. When the prefix is used, the name of the database would look as follows:

  Purpose of cache	No prefix	Valid prefix
  Query responses	queries.db	<ClientDatabasePrefix>_queries.db
  Offline Mutations	offlineMutations.db	<ClientDatabasePrefix>_offlineMutations.db
  Subscriptions metadata for Delta Sync	subscriptionMetadataCache.db	<ClientDatabasePrefix>_subscriptionMetadataCache.db

  • The ClientDatabasePrefix can be passed via awsconfiguration.json that is generated from the AWS AppSync Console and Amplify CLI.

     "AppSync": {
      "Default": {
        "ApiUrl": "https://xyz.appsync-api.us-east-2.amazonaws.com/graphql",
        "Region": "us-east-2",
        "AuthMode": "API_KEY",
        "ApiKey": "da2-xyz",
        "ClientDatabasePrefix": "MyAppSyncAPIName_API_KEY"
      }
    }
    

    The AWSAppSyncClient object can be constructed as follows:

    let serviceConfigAPIKey = try AWSAppSyncServiceConfig()
    let cacheConfigAPIKey = try AWSAppSyncCacheConfiguration(useClientDatabasePrefix: true,
                                                                appSyncServiceConfig: serviceConfigAPIKey!)
    let clientConfigAPIKey = try AWSAppSyncClientConfiguration(appSyncServiceConfig: serviceConfigAPIKey!,
                                                             cacheConfiguration: cacheConfigAPIKey!)
    let clientAPIKey = try AWSAppSyncClient(appSyncConfig: clientConfigAPIKey!)

• Deprecated clearCache() please use clearCaches(options:) instead. This new method will clear the query responses, offline mutations and subscriptions metadata by default and the options parameter can be used to fine-tune the operation.

2.12.2

Bug Fixes

• Fix a bug where subscriptions would be blocked from starting again after being cancelled. See issue #249

2.12.1

Misc. Updates

• Make network reachability provider mockable See PR #245. Thanks @gleue! 🎉

Bug Fixes

• Improved internal handling of subscription cancellation and disconnect.
  • With this update, the cancellation behavior for subscription is more robust in both cases - when developer issues cancel and when SDK notifies connectionError in the statusChangeHandler and resultHandler
  • As a best practice, we recommend that if you do not want to receive any more callbacks on the statusChangeHandler and resultHandler for the subscription, issue a cancel which would immediately stop all communication to the watcher.
  • Once cancel is issued, no notifications or error callbacks will be given to the watcher. If the watcher object is not reference from application code, it will internally issue a cancel and ensure that no callbacks are given.

2.12.0

Bug Fixes

• Upgraded SQLite.swift to 0.11.6 to fix a bug in persistent cache handling. See issue #211. Apps that declare direct dependencies on SQLite.swift must update the pods to avoid a conflict and get the fixed version. This new requires that AppSync be built using Xcode 10.2 or later.

Misc. Updates

• Breaking Build Environment Changes

  • AppSync SDK for iOS now requires Xcode 10.2 or later to build.

• Other changes

  • Updated AWS SDK dependencies to 2.9.6
  • Updated SQLite.swift to 0.11.6

2.11.1

Bug Fixes

• Fixed a bug where cancelled mutations would not be cleared from the persistent store and would be sent to service on app restart. See issue #187

Misc. Updates

• Updated AWS SDK dependencies to 2.9.5

2.11.0

Misc. Updates

Behavior Change for Mutation Queue

• With this update, the internal operation logic of how mutations are processed is updated
• The mutation queue in the previous SDKs, depended on notification from reachability to determine if the mutations could be sent to the service; in the new behavior we are more aligned to Apple's Designing for Real-World Networks guidance
• The AppSync client will now always attempt to make a mutation request regardless of the network state
• One the network response comes back, the SDK will inspect the error from NSURLSession and determine if the error was due to network not available, host not found or DNS lookup failed. If it was, the SDK will schedule a retry timer responsible to retry the request which will grow exponentially with every attempt
• The retry handler will also watch for notification from reachability to determine if network is available again; in cases where SDK does get the notification, it will preempt the timer and make the request right away
• If the notification is not received, the timer will continue to retry the request. The polling interval is capped at 5 minutes to ensure that attempts are made at frequent attempts while respecting resources on device
• The mutations will retried at these intervals repeatedly until they are successful or cancelled
• AppSync client will ensure that it works with auth clients who return the correct errors. The AWS credential providers are validated to check if they return the correct NSURLSession errors so that retry can be scheduled
• If using a custom auth client, while invoking the error callback for auth provider, it is recommended to include NSURLErrorDomain in the domain field and the indicated error code in code field.
• There are no API changes required to update to this behavior

2.10.4

New Features

• The AppSyncClient now supports specifying retry strategy using the retryStrategy parameter in AWSAppSyncClientConfiguration. You can choose between aggressive and exponential(default selection).

Bug Fixes

• Mark uniqueIdentifier field in AWSSubscriptionWatcher as public which was incorrectly marked private in previous version.

2.10.3

New Features

• The AppSyncClient's subscribe method now accepts an optional statusChangeHandler. If provided, then the AWSAppSyncSubscriptionWatcher returned by the subscribe method will invoke that method when it is notified of changes to the state of the underlying MQTT client. AWSAppSyncSubscriptionWatcherStatus for a description of the statuses and their progression. Thanks @fans3210, @shannon-hager-skookum, and @achager for contributing your thoughts to the original request (Issue #42) and to @MarioBajr for contributing the original implementation on PR #75.
• Added a queuedMutationCount property to AppSyncClient (Issue #192)

Bug fixes

• Fixed incorrect AWSCore dependency version in podspec (Issue #190)
• Fixed data races in AppSyncMQTTClient that were causing crashes (Issue #184)

Misc. Updates

• Added AWSAppSyncClientLogFormatter utility class. Developers who want to use it can add it to the appropriate logger. For example, a configuration like:

  AWSDDLog.sharedInstance.logLevel = .verbose
  AWSDDTTYLogger.sharedInstance.logFormatter = AWSAppSyncClientLogFormatter()
  AWSDDLog.sharedInstance.add(AWSDDTTYLogger.sharedInstance)

  would output log messages like:

  2019-03-04 07:21:32.131-0800 [I AWSAppSyncClient.init(appSyncConfig:reachabilityFactory:), L75] Initializing AppSyncClient
  2019-03-04 07:21:32.135-0800 [V AWSPerformMutationQueue.init(appSyncClient:networkClient:reachabiltyChangeNotifier:cacheFileURL:), L24] Initializing AWSPerformMutationQueue
  2019-03-04 07:21:32.135-0800 [V AWSPerformMutationQueue.resume(), L95] Resuming OperationQueue
  

  Please note that verbose logging is quite verbose, and there is a significant difference between verbose and debug. We will be making debug more useful as we go. (See Issue #145)

  As always, we recommend turning off logging when deploying to production.

• Added some verbose logging around mutation queue handling and subscription connections; minor log additions elsewhere

• Minor dead code removal & miscellaneous cleanup

2.10.2

Bug fixes

• Fixed a bug where queries with dots (".") in the arguments were not being properly cached (Issue #110, #165)
• AWSAppSyncClient.perform(mutation:queue:optimisticUpdate:conflictResolutionBlock:resultHandler:) now properly invokes its result handler callbacks on the supplied queue instead of always using DispatchQueue.main

2.10.1

Bug fixes

• Prepopulate the queries cache with an empty QUERY_ROOT record, to allow optimistic updates of the cache where no queries have been previously performed. (Issue #92, #101)

• Fix how "cache hits" are determined in queries, to match Apollo behavior. A "cache hit" is defined as all members of the selection set having a non-nil value. For a simple query, (e.g., the HeroNameQuery of the StarWars API), that is an easy mental map:

  Cache hit

  {
    "QUERY_ROOT": { "hero": "#hero" },
    "#hero": { "hero": {"name": "R2-D2", "__typename": "Droid"} }
  }

  Cache misses

  {}
  
  { "QUERY_ROOT": null }
  
  
  { "QUERY_ROOT": {} }
  
  {
    "QUERY_ROOT": { "hero": "#hero" },
    "#hero": { "hero": null }
  }
  
  // Misses because type data is incomplete
  {
    "QUERY_ROOT": { "hero": "#hero" },
    "#hero": { "hero": {"name": "R2-D2"} }
  }

  For more complex queries (like the TwoHeroesQuery), only all values being non-nil will result in a cache hit: Cache Hit

  {
    "QUERY_ROOT": {
      "hero": "#hero",
      "hero(episode:EMPIRE)": "#hero(episode:EMPIRE)"
    },
    "#hero": {"name": "R2-D2", "__typename": "Droid"},
    "#hero(episode:EMPIRE)": {"name": "Luke Skywalker", "__typename": "Human"}
  }

  Cache Misses

  {}
  
  { "QUERY_ROOT": null }
  
  
  { "QUERY_ROOT": {} }
  
  {
    "QUERY_ROOT": { "hero": "#hero" },
    "#hero": { "hero": null }
  }
  
  {
    "QUERY_ROOT": {
      "hero": "#hero"
    },
    "#hero": {"name": "R2-D2", "__typename": "Droid"}
  }

  These definitions match the existing Apollo behavior, as verified in additional tests against the unmodified Apollo codebase.

Misc. Updates

• Updated CloudFormation template to include S3 buckets and associated configuration to support complex object integration tests, and added integration tests for S3 uploads and downloads.

2.10.0

Bug fixes

• Merged Apollo iOS PR #427 to fix incompatibility with EnumeratedIterator in latest Xcode 10.2 beta.
• Fixed an issue where performing a mutation with no parameters would crash clients using a backing database. Issue #33
• Reduced database contention to fix crash resuming from background (See Issue #160). Thanks @larryonoff for contributing to this fix! 🎉

Misc. Updates

AWSAppSyncCacheConfiguration

AppSync persistent caches for queries (used by the Apollo store), mutations, and subscription metadata are now stored in separate files. A new AWSAppSyncCacheConfiguration API has been added that allows clients to specify persistent caches for all, some, or none of these caches:

// Specify persistent caches that live in the app's Cache directory
let cacheConfiguration = try AWSAppSyncCacheConfiguration()

// ... or specify persistent caches that live in `rootDirectory`
let cacheConfiguration = try AWSAppSyncCacheConfiguration(withRootDirectory: rootDirectory)

// ... or specify a database path for the query cache and the subscriptionMetadata cache, but an in-memory cache for mutation queue
let cacheConfiguration = AWSAppSyncCacheConfiguration(offlineMutations: nil,
                                                      queries: queriesDatabasePath,
                                                      subscriptionMetadataCache: subscriptionMetadataDatabasePath)

// ... or specify all caches to be in-memory
let cacheConfiguration = AWSAppSyncCacheConfiguration.inMemory

// ... then use the cache config in the AWSAppSyncClientConfiguration constructor
let appSyncConfig = try AWSAppSyncClientConfiguration(appSyncServiceConfig: serviceConfig, cacheConfiguration: cacheConfiguration)
let appSyncClient = AWSAppSyncClient(appSyncConfig: appSyncConfig)

// Alternately, specify all in-memory caches by passing no `cacheConfiguration`
let appSyncConfig = try AWSAppSyncClientConfiguration(appSyncServiceConfig: serviceConfig)
let appSyncClient = AWSAppSyncClient(appSyncConfig: appSyncConfig)

Migration

Clients can migrate to the new AWSAppSyncCacheConfiguration with a utility method that performs a one-time move of data from the previous databaseURL to the new cache configuration directory:

// Specify persistent caches that live in the app's Cache directory
let cacheConfiguration = try AWSAppSyncCacheConfiguration()

let databaseURL = // whatever your old databaseURL was

// Upon successful completion, this method sets a flag in UserDefaults, making it safe
// to call at startup for as long as this method exists.
AWSAppSyncCacheConfigurationMigration.migrate(from: databaseURL, to: cacheConfiguration)

• Breaking API Changes

  • AWSSQLLiteNormalizedCacheError has been renamed to AWSAppSyncQueriesCacheError. Error conditions during manipulations of the Apollo store will now throw this type.

• Deprecations

  • AWSSQLLiteNormalizedCache is deprecated and will be removed in an upcoming minor version of AWSAppSync, as that implementation is an internal detail. Clients that wish to do cleanup of database files can use AWSAppSyncCacheConfiguration to get the path of the appropriate database file.
  • The databaseURL option to AWSAppSyncClientConfiguration is deprecated. Please use the cacheConfiguration option (See above)
  • The MutationCache protocol is deprecated because it is unused.

2.9.2

New Features

• Added an AWSAppSyncClient.clearCache() method to clear the local Apollo cache. See Issue #36, PR #141 Thanks @larryonoff! 🎉

Bug fixes

• AppSyncClient.sync() now properly invokes its subscription callbacks on the supplied handlerQueue instead of always using DispatchQueue.main

Misc. Updates

• AWSAppSync now uses Xcode 10.1 to build its Carthage binaries. This will make the binaries compatible with Swift 4.2.1. Projects that have not yet upgraded to use Swift 4.2.1 will fall back to building from source.
• The AWSAppSync target no longer specifies values for VALID_ARCH in its build settings but instead uses defaults. See PR#156 Thanks @larryonoff! 🎉

2.9.1

Bug Fixes

• Updated the Cartfile to depend on the correct version of the AWS iOS SDK. (Note, this is advisory only; we do not retrieve dependencies via Carthage.)
• Added Pods to source control so Carthage users (or anyone else who builds from source) will no longer need to issue a pod update before building (#150)

2.9.0

Bug Fixes

• Mutation queue handling is rewritten to use OperationQueue, to fix cases where mutations would either deadlock (#81), or not execute (#106). Thanks @larryonoff! 🎉
• S3Objects now correctly upload whether they are included as part of a mutation's parameters or an input type (#122)

Misc. Updates

• Breaking API Changes

  • AWSPerformMutationOperation was public, now it's internal
  • AWSAppSyncClient.perform now returns Cancellable instead of AWSPerformMutationOperation

• Refactored internal network change notifications (#139)

• Refactored structure & tests to make future maintenance easier. As part of this, we deprecated the AWSAppSyncClientInfo class in favor of the AWSAppSyncServiceConfigProvider protocol. We provide a default implementation AWSAppSyncServiceConfig. AWSAppSyncClientInfo will be removed in a future minor version.

  • Thanks to @larryonoff for contributing code and PR feedback to this refactor! 🎉

• Refactored tests into Unit and Integration tests. Currently, any test that requires network activity is placed in Integration tests, even if the test hits localhost and not a valid service.

  • Updated the README to include new instructions for setting up your integration test environment.
  • The project now includes an AWS CloudFormation template to bootstrap your test setups. This will be updated in the future to include S3 buckets and associated configuration to support complex object integration tests.

2.8.0

Misc. Updates

• Use Swift 4.2's Float.random(in:) instead of arc4random() to generate request retry jitter. See PR #108. Thanks @larryonoff! 🎉
• Added SwiftLint to project. See PR #121 and issue #107. Thanks @larryonoff! 🎉
• Increase stability of the integration tests; removed subscription integration test since its functionality is now covered by sync operation test.
• Upgraded SQLite.swift to 0.11.5, which fixes compiler warnings when compiling AWSAppSync in Xcode. Thanks @larryonoff! 🎉
• Breaking API Changes
  • SyncConfiguration:
    • The type changed from a class to a struct
    • The initializer parameter is now optional, and the previous defaultSyncConfiguration method has been removed. Create a default configuration by invoking the initializer with no arguments, SyncConfiguration()

2.7.0

New Features

• Added support for Delta Sync Feature Delta Sync allows you to perform automatic synchronization with an AWS AppSync GraphQL server. The client will perform reconnection, exponential backoff, and retries when network errors take place for simplified data replication to devices. For more details, please refer documentation.

Bug Fixes

• Fixed issue where if a timeout error occurred due to lack of network availability, the callback would not be given back to the developer. See issue #91

Misc. Updates

• Officially convert project to Swift 4.2. Previously, the project used some Swift 4.2 idioms even though the SWIFT_VERSION was officially set to 3. This change makes the support explicit in the project files and README.
• Updated SwiftReachability dependency to 4.3.0. (See PR #84)[#84] Thanks @larryonoff! 🎉
• Replaced generic struct based AWSAppSyncClientError by a typed enum. (See PR #35)[#35] Thanks @MarioBajr! 🎉

2.6.24

Misc. Updates

• AWSAppSync now depends on AWSCore version 2.7.x instead of 2.6.x.

2.6.23

Bug Fixes

• Resolved retain cycles in AWSAppSyncClient which allow the instance to be deallocated. See PR#88 Thanks @ifabijanovic 🎉
• Resolved retain cycle in underlying MQTT client. Source

2.6.22

Enhancements

• Allow multiple active subscriptions while using API_KEY auth.
• Add retry logic for the HTTP service calls.
• Allow responses to have missing fields if they are optional.
• Fix issue with optimistic writes which would incorrectly throw JSONDecodingError.missingValue error. See issues #51 #8
• Fix warnings imposed by iOS 12. See PR#71

2.6.21

Enhancements

• Improve subscriptions logic to use a single shared queue and avoid delay between multiple subscriptions. See PR#28 Thanks @MarioBajr! 🎉

2.6.20

Enhancements

• Allow asynchronous fetching of User Pools / OIDC auth token. See PR#62 Thanks @JohnRbk 🎉
• Integrate logging with AWSDDLog. To print logs from the SDK, follow instructions mentioned here.

Bug Fixes

• Fixed a bug in loading configuration from awsconfiguration.json
• Fixed a bug where receiving a non String or JSON object would cause SDK to crash. The SDK would now instead log an error message.

2.6.19

New Features

• Add support for AWS AppSync configuration through awsconfiguration.json in AWSAppSyncClient.

2.6.18

Enhancements

• Improve connection handling of underlying MQTTClient.

2.6.17

Enhancements

• Improve performance of AWSAppSyncMQTTClient. See PR#34
• AWSNetworkTransport modifications to enable the ability to mock server. See PR#40
• Fixed typo in AWSGraphQLSubscriptionResponse initializer and variable. See PR#29

Bug Fixes

• Preventing IAM signature requests from blocking the main thread. See PR#32
• Call the AWSAppSyncClientConfiguration connectionStateChangeHandler which was previously un-used. See PR#30

2.6.16

New Feature

• Add OpenID Connect (OIDC) support as an authorization option.

Bug Fixes

• Fix SQLite lock issue. See PR#20
• Renamed private AWSSRWebSocket classes in order to avoid duplicated symbols. See PR#21
• Respect the requested callback queue when invoking subscription callbacks. See PR#22

2.6.15

Bug Fix

• Fixed a crash in cancel method of SubscriptionWatcher by adding a safer workflow. See PR #11

2.6.14

New Features

• Expose whether a result was served from service or cache. Source
• Watchers are now triggered while writing to cache from a transaction. Source

Bug Fixes

• Fixed a bug in cancel method of SubscriptionWatcher where calling cancel and then restarting a subscription in the same view controller would cause a crash.