-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while configuring storage category #5335
Comments
@perrydev17 - It look like the stack trace is from a browser. Are you able to reproduce this on any other platform? If so, can your provide the stack trace from that platform? |
hi @Jordan-Nelson also not able to run in other platforms (Android)
separately, I was able to run the debug mode (web) with no error, but got the error with flutter run |
@perrydev17 Before running on Android you will need to follow the Android platform setup steps here: https://docs.amplify.aws/flutter/start/platform-setup/#android I am not able to reproduce the error you are seeing on web. Can you provide the following info:
|
I'm closing this issue as we did not hear back. Please feel free to open a new issue if the issue is not resolved. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Description
hi, I am getting an error when trying to add the storage plugin into the flutter app, I confirm auth is working as expected, but storage is erroring out
amplify_flutter: ^2.0.0
amplify_auth_cognito: ^2.0.0
amplify_authenticator: ^2.0.0
amplify_storage_s3: ^2.0.0
this is the code in main.dart
in amplifyconfiguration.dart I have
"storage":{ "aws_region":"us-east-1", "bucket_name":"xxx" <- the bucket was created during amplify gen2 setup },
and this is the error crashing the app
thanks in advance!
Categories
Steps to Reproduce
app crash and can't be loaded upon the line addPlugin(storage), I have tried both method addPlugins and addPlugin
Screenshots
No response
Platforms
Flutter Version
3.4.1
Amplify Flutter Version
^2.0.0
Deployment Method
Amplify CLI
Schema
No response
The text was updated successfully, but these errors were encountered: