Richard McClellan

Another customer requested this feature in https://github.com/aws-amplify/amplify-android/issues/1328, but for Akamai, rather than Cloudfront.

At some point we would like to add support for this, but we don't have any timelines yet. For now, please use the SDK ([documentation](https://docs.amplify.aws/sdk/push-notifications/getting-started/q/platform/android#connect-to-your-backend))

Hi @deveshmittalncs, this sounds like a bug in the library. When you sign out, it should clear cookies so that you aren't automatically signed in to the same account on...

@raphkim's change fixed the sign out flow so that the Cognito session cookies are cleared on sign out. However, it appears that cookies from federated providers (Google, Facebook, etc) are...

I chatted offline with @richardissuperman to understand his use case a little more. His Android application integrates with a preexisting data model, where the primary keys are not in UUID...

> > This use case could be solved by removing the UUIDv4 requirement on the id field. > > @richardmcclellan what about the use case of Amazon DynamoDB table having...

it is possible to load the configuration file from different locations. We do this in our tests. You can select a config to load at runtime, and then use an...

This is on the roadmap, stay tuned!

> When a user signs in using the standard Auth APIs Did you use `Amplify.Auth.signIn` or `Amplify.Auth.signInWithWebUi`?

Got it. I believe this is a limitation of `AWSMobileClient` - we don't support basic sign in **and** hosted UI sign in in the same app, you have to choose...