awslabs / awslabs/aws-mobile-appsync-sdk-android
Implement callback to specify a custom retry policy
- Dominant language
- Java
- Stars
- 106
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
I am using AppSync with Cognito. The app I am building allows the user to make some mutations offline, even before the authentication is complete. Basically there is no need for the user to use the credentials, but those are auto-generated, and the app automatically sign-up and sign-in.
So, when the user starts the app for the first time, offline, and makes some mutations, as soon as the device goes online, the mutations will be sent to the cloud, but most of them are going to fail, cause the authentication is usually slower.
So my question is: can I prevent the mutations to be sent till the authentication is valid?
If that's not possible, is it possible to cancel all the enqueued mutations?
Contributor guide
Research direction
Start by tracing how offline mutations are queued and sent when connectivity returns, and how AppSync authentication completion is exposed. Clarify whether the intended result is delaying queued mutations, cancelling them, or adding a custom retry callback; done should include a decided API and tests for the selected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, graphql, java
- Domain
- api, authentication, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100