Tyler-Larkin

Results 156 comments of Tyler-Larkin

Hello @DanBeltranuwu, I've attempted to reproduce the issue on Flutter 2.6.3 and was not able to reproduce the issue. I used the following code which I believe is similar enough...

Hello @DanBeltranuwu, thanks for confirming! Let's rule out any conflicts with other packages by creating a minimal reproducible example: 1. Remove all non-Amplify dependencies from your pubspect.yaml 2. Run `flutter...

Hello @DanBeltranuwu I just wanted to confirm, you are unable run this minimal reproducible example locally as it would generate unwanted analytic events? Or is there a different reason?

Hello @DanBeltranuwu, can you create a sandbox amplify environment where you can safely test this minimal reproducible example. If that is also not possible can you please provide a minimal...

Hello @rathoregee, we have an open [feature request](https://github.com/aws-amplify/amplify-flutter/issues/1318) to add additional logging customization, such as disabling platform/category specific logging. In the meantime if your IDE supports it you can use...

Hello @rathoregee, unfortunately we do not have that feature at this time. The feature request I linked above would cover that use case.

Hello @akshaykanhasoft1, I've been unable to reproduce the issue while using the same SignInRedirectURI, SignOutRedirectURI, and CFBundleURLSchemes that you provided. Could you please verify your iOS deployment versions are at...

Helllo @iosephmagno, I can mark this issue as a feature request, but currently [S3 responses for DeleteObject](https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html#API_DeleteObject_ResponseElements) don't distinguish between a existing and non-existing path (unless there are permission or...

Hello @ruossn, thanks for taking the time to open up this issue. Since the exception is intermittent it might be difficult for us to reproduce and identify the root cause,...

Hello @ruossn, as an update I've gotten the following errors over the past couple of days, but no SignedOutException. ``` UnknownException { "message": "unable to send GraphQLRequest to client.", "underlyingException":...