Mutable Alligator

@achager PR #198 addresses this issue.

Hi Riad @kwantam, I am not very sure about my understanding. But here are my findings. Please correct me if I'm wrong. 1. I know that we do time measurements...

Thank you @Cyan-pactera for reporting to us. Sorry for the inconvenience caused. As you pointed out, the SDK only supports RSA for key exchange though the IoT service supports ECDSA....

@mendirattanishant Sorry for the delayed response. 1) Custom Auth: Have you considered using Custom Auth where you can setup a lambda function which validates the token and its signature and...

@vladspreys Thank you for reporting to us. The `SignUpResult` that is returned by `AWSMobileClient.signUp` method is a result object that lives in the `AWSMobileClient` SDK and is different from the...

@thomers Sorry for the inconvenience caused. I will go over your questions one by one. 1) Should the configuration be stored in awsconfiguration.json or Info.plist? (Which has precedence?) `awsconfiguration.json` takes...

@thomers @BillBunting Sorry for the inconvenience caused. We are discussing this issue internally and we will post an update here about our findings. Thank you for your patience.

@midaslefkowitz Thank you for reporting to us. This is currently a limitation of `TransferUtility`. The current design does not allow us to use a different network connection type for each...

@midaslefkowitz Have you tried using `TransferUtility.resumeAllWithType()` to resume the paused transfers? When doing so, you could construct a `TransferUtility` instance with the preferred network connection type.

@midaslefkowitz You are right. The network connection type is being stored in the transfer database. A transfer if started with a particular network connection type, for example WiFiOnly will need...