Instance of 'UnknownSmithyHttpException' on adding amplify_analytics_pinpoint: ^2.2.0
Description
Note: This project has not be created using amplify cli. I used an existing pinpoint project with my flutter app. I have provided the input configuration through amplifyconfiguration.dart providing the app id and the region under pinpointAnalytics
I see the error being thrown here
This line to be specific
This is how the error is being logged and there is no useful recovery suggestion
Flutter doctor
Please let me know if I can provide more information. I need amplify pinpoint analytics to track events and would really appreciate help with this
Categories
- [X] Analytics
- [ ] API (REST)
- [ ] API (GraphQL)
- [ ] Auth
- [ ] Authenticator
- [ ] DataStore
- [ ] Notifications (Push)
- [ ] Storage
Steps to Reproduce
- Add a valid amplifyconfiguration.dart file to a flutter project make sure to include the awsPinpointAnalyticsPlugin configuration
- Configure amplify as shown in the image above (the graphql config is optional its relevant to my application)
- Run the app
Screenshots
Platforms
- [X] iOS
- [X] Android
- [ ] Web
- [X] macOS
- [ ] Windows
- [ ] Linux
Flutter Version
3.22.0
Amplify Flutter Version
2.2.0
Deployment Method
Custom Pipeline
Schema
No response
Sorry that you are facing this issue and thanks for reporting it. We will look into this and get back to you when we have updates.
Hello @vipinkashyap can you please verify that your IAM Policy has been updated to as described here. This will need to be done for both your Guest role and Authenticated role which can be found here:
AWS Console -> Cognito -> Identity pools -> Identity pool name -> User access
In the meantime I'll look into why this documentation is excluded in Flutter.
I can confirm that the steps you've detailed work . I am able to now use pinpoint analytics. Thank you!
@vipinkashyap thanks for confirming and gald that the issue is resolved. I will leave this issue open to update the documentation and close it after that.
I'm going to close this issue as the documentation is updated. please feel free to open a new issue if you have any other questions.
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.