When an error is triggered within the Datastore error handler, there isn't any mechanism to obtain the original request for the client to retry. It's necessary to establish a means to access the request for the client to retry any failed requests effectively.
final datastorePlugin = AmplifyDataStore(
modelProvider: ModelProvider.instance,
// Error handler for any error occurs during datastore save
errorHandler: (error) {
print('AWS Error: $error');
},
syncExpressions: syncExpression);
Categories
[ ] Analytics
[ ] API (REST)
[ ] API (GraphQL)
[ ] Auth
[ ] Authenticator
[X] DataStore
[ ] Notifications (Push)
[ ] Storage
Steps to Reproduce
1.Create models as in schema
Initialize Datastore
Do Datastore.save()
Fails all incoming request in appsync or intercept iOS simulator request using any interceptor tool like Charles proxy OR Proxyman.
Analyze AmplifyException instance to retrieve original request.
Screenshots
No response
Platforms
[X] iOS
[ ] Android
[ ] Web
[ ] macOS
[ ] Windows
[ ] Linux
Flutter Version
3.19.0
Amplify Flutter Version
1.7.0
Deployment Method
Amplify CLI
Schema
type Todo @model {
id: String!
message: String!
emails: [String!]!
expirationUnixTime: AWSTimestamp
}
Description
When an error is triggered within the Datastore error handler, there isn't any mechanism to obtain the original request for the client to retry. It's necessary to establish a means to access the request for the client to retry any failed requests effectively.
Categories
Steps to Reproduce
1.Create models as in schema
AmplifyException
instance to retrieve original request.Screenshots
No response
Platforms
Flutter Version
3.19.0
Amplify Flutter Version
1.7.0
Deployment Method
Amplify CLI
Schema