minbi

Thank you for providing valuable insight into your experience and use of the SDK. We will incorporate this into our improvement items.

Hi @johnmurphy01 , Thanks for the report. We will investigate this issue.

The answer is probably that is not supported, but I have tagged @rohandubal for a better answer of the current state of the SDK.

Hi @vermasumeet1982 , Thanks for reporting this issue to us. We'll update you when we know more.

Hi @Joseph82 , Just to clarify, are you using Cognito Userpools for sign-in? If so, You may look at using AWSMobileClient for authentication with Userpools because it supports blocking calls...

I believe the offline mutation shouldn't be blocked since in that case the SDK shouldn't be attempting to grab credentials when offline is detected. I'll let @cbommas chime in one...

So, when the SDK grabs credentials from AWSMobileClient, it will block if needs fresh-er credentials, thus waiting for you to sign-in, if required. Unless the mutation has a timeout that...

Ah, apologies for not being clear. In my current proposal, `AWSAppSyncClient` would be using `AWSMobileClient` as the object that provides the Userpools tokens through the `CognitoUserPoolsAuthProvider` interface. Therefore when the...

You would specify it in the builder. One way to do it would be as follows: ```java client = AWSAppSyncClient.builder() .context(context) .awsConfiguration(awsConfiguration) .cognitoUserPoolsAuthProvider(new CognitoUserPoolsAuthProvider() { @Override public String getLatestAuthToken() {...

The `PersistentMutationsCallback` will notify you of failures in offline mutation queue. You can attach it to the AppSync client when building it. See [here](https://github.com/awslabs/aws-mobile-appsync-sdk-android/blob/master/aws-android-sdk-appsync/src/main/java/com/amazonaws/mobileconnectors/appsync/AWSAppSyncClient.java#L359)