aws-mobile-appsync-sdk-android

• Fixed issue 292.

• Fixes following issues:
  • issue 279
  • issue 317

Fixes https://github.com/awslabs/aws-mobile-appsync-sdk-android/issues/306.

Release 2.11.0

The 2.x releases use MQTT as a subscription transport, instead of WebSockets, as in 3.x.

Most users should use the latest release of 3.x.

Bug Fixes

The 2.11.0 release contains a back-port of support for Android Studio 4.0.0+ / Android Gradle Plugin 4.0.0+ / Gradle 6+. See https://github.com/awslabs/aws-mobile-appsync-sdk-android/issues/270.

Release 3.1.0

Bug Fixes

Adds support for Android Studio 4.0.0+ / Android Gradle Plugin 4.0.0+. Addresses incompatibilities with Gradle 6+. See https://github.com/awslabs/aws-mobile-appsync-sdk-android/issues/270.

Release 3.0.1

Bug Fixes

• Added fix to preserve null list items when parsing the response. See issue #156 for details.

Release 3.0.0

Enhancements

• 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.

• Adopted Semantic versioning

  • Starting with version 3.0.0 AppSync AWS Android SDK will follow sematic versioning.

Misc. Updates

• AWSAppSync now depends on AWSCore version 2.16.3 instead of 2.16.1.

Release 2.10.1

Enhancements

• Make GraphQLStoreOperation.Callback a public interface, so the AWSAppSyncStore asynchronous operations can be passed with a callback. Thanks @cjami for the contribution. See PR #193 for details.

Misc. Updates

• AWSAppSync now depends on AWSCore version 2.16.1 instead of 2.13.5.

Bug Fixes

• If an App Sync subscription attempts to be executed while in a non-Idle state, it will now pass the error back through the callback vs. crashing the app with a runtime exception. See issue#202

Enhancements

• Add new validations in AWSAppSyncClient.Builder.
  • Throw RuntimeException when Android context passed in is null.
  • Throw RuntimException when there is no valid AuthMode object passed in.

Misc. Updates

• AWSAppSync now depends on AWSCore version 2.13.5 instead of 2.13.4.

New Features

• Support multiple authorization modes for a single AWS AppSync GraphQL endpoint.
• Introduced clientDatabasePrefix(String) 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). When the prefix is used, the name of the database would look as follows:

• 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:

      AWSAppSyncClient awsAppSyncClient = AWSAppSyncClient.builder()
                .awsConfiguration(awsConfiguration)
                .useClientDatabasePrefix(true)
                .build();
  

• Alternatively, the ClientDatabasePrefix can be passed via the AWSAppSyncClient.Builder.

     AWSAppSyncClient awsAppSyncClient = AWSAppSyncClient.builder()
                    .context(getApplicationContext())
                    .apiKey(new BasicAPIKeyAuthProvider("da2-apiKey"))
                    .serverUrl(serverUrl)
                    .region(region)
                    .useClientDatabasePrefix(true)
                    .clientDatabasePrefix("MyAppSyncAPIName_API_KEY")
                    .build();
  

Misc. Updates

• AWSAppSync now depends on AWSCore version 2.13.4 instead of 2.13.2.

Bug Fixes

• Fixed a bug with inconsistent capitalization of class names in generated code that represent GraphQL input types. See PR #150 for details.
• Fixed a bug with inconsistent capitalization of variables in generated code that represent fields for GraphQL types. See PR #172 for details.

Enhancements

• AWS AppSync plugin for gradle is now compatible with Gradle version 5.x. See issue#91 for details. To consume these changes make sure to upgrade the appsync plugin version, which can be found in the project-level build.gradle, to classpath 'com.amazonaws:aws-android-sdk-appsync-gradle-plugin:2.8.+'

Bug Fixes

• This release adds back the public methods namely, cacheKey and CacheFieldValueResolver that were removed as part of release 2.8.0. These methods have been deprecated and will be removed in the next minor version.

Bug Fixes

• All the GraphQL input types now derive from the base class InputType. cacheKey method from ResponseField is no longer used to compute the cache key and is being deleted. CacheFieldValueResolver now accepts an instance of CacheKeyBuilder which is used to compute cache keys instead of the cacheKey method. See issue #103

Bug Fixes

• Fixed a bug that cause NullPointerException in the ApolloServerInterceptor. See PR #146 Thanks @alanvan0502 !
• Sanitized useragent string of unicode characters that caused requests to fail. The unicode characters in this case came from the platform name (TM) symbol. See PR #146 Thanks @alanvan0502 !

Misc. Updates

• AWSAppSync now depends on AWSCore version 2.13.2 instead of 2.13.0.

Bug Fixes

• Fixed a bug that caused cursors to remain open in certain scenarios. See PR #141 Thanks @alanvan0502 ! See issue #140

Misc. Updates

• AWSAppSync now depends on AWSCore version 2.13.0 instead of 2.12.1.

Misc. Updates

• AWSAppSync now depends on AWSCore version 2.12.1 instead of 2.11.0.

Bug Fixes

• Adjusted network connectivity check in mutation processing logic. See issue #108, issue #121
• Fixed NoSuchElementException in Subscription Reconnection logic. See issue #114.

Bug Fixes

• Fixed a memory leak in subscriptionsById map. See issue #111.
• Prevent a NPE on the userCallback when canceling a subscription. See issue #114.

Misc. Updates

• AWSAppSync now depends on AWSCore version 2.11.0 instead of 2.10.1.
• Added support to check if mutation queue is empty and to clear mutation queue. See issue #96, and issue #101

Bug Fixes

• Fixed bug in mutationQueueExecutionTimeout method. See issue #105
• Fixed bug in mutation processing logic to handle case where cancel is called in the mutation callback. See issue #102

Misc. Updates

• AWSAppSync now depends on AWSCore version 2.10.1 instead of 2.10.0.

Bug Fixes

• Fixed bugs in Conflict resolution logic. See issue #50, issue #95, and issue #98