-
Notifications
You must be signed in to change notification settings - Fork 119
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
DataStoreExeption can not sync added types #2471
Comments
Error disappeared yesterday evening, I added 300 items to mew model. And it returned again, the same error. The reason is not in auth, it works correct. In example it was just experiment. |
additional error, it is printed after first error: amplify:aws-datastore com.app.danskassistent.android I Orchestrator transitioning from SYNC_VIA_API to LOCAL_ONLY |
Hi, any updates on this issue? I have the same problem.
|
any updates? |
I'm sorry for the delays on this ticket. Looking at the initial code snippet, I'd like to suggest at least a few changes so that we can rule them out. Amplify.configure should be placed in the application's Next, there are at least some models like |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Before opening, please confirm:
Language and Async Model
Kotlin, Kotlin - Coroutines
Amplify Categories
DataStore
Gradle script dependencies
Environment information
Please include any relevant guides or documentation you're referencing
No response
Describe the bug
Type Word works correctly like Queryes. Data store sync works correct.
But for other types which was added later I received next error in console.
Not only IrregularWord or IrregularSound types invoke to error, but any other type which I they to add.
So every type which I try to add to excited early types invoked the same error.
I tryed rebuild api, or update conflict detection (is is enable). Nothing can helps.
If I remove recently added types and leve only Word and Query it works correct
Reproduction steps (if applicable)
Code Snippet
Log output
amplifyconfiguration.json
{
"UserAgent": "aws-amplify-cli/2.0",
"Version": "1.0",
"api": {
"plugins": {
"awsAPIPlugin": {
"danskassistent": {
"endpointType": "GraphQL",
"endpoint": "https://xxxxx.appsync-api.eu-central-1.amazonaws.com/graphql",
"region": "eu-central-1",
"authorizationType": "AMAZON_COGNITO_USER_POOLS",
"apiKey": "xxxxx"
}
}
}
},
"auth": {
"plugins": {
"awsCognitoAuthPlugin": {
"UserAgent": "aws-amplify-cli/0.1.0",
"Version": "0.1.0",
"IdentityManager": {
"Default": {}
},
"AppSync": {
"Default": {
"ApiUrl": "https://xxxxx.appsync-api.eu-central-1.amazonaws.com/graphql",
"Region": "eu-central-1",
"AuthMode": "AMAZON_COGNITO_USER_POOLS",
"ClientDatabasePrefix": "danskassistent_AMAZON_COGNITO_USER_POOLS"
},
"danskassistent_API_KEY": {
"ApiUrl": "https://xxxxx.appsync-api.eu-central-1.amazonaws.com/graphql",
"Region": "eu-central-1",
"AuthMode": "API_KEY",
"ApiKey": "xxxxx",
"ClientDatabasePrefix": "danskassistent_API_KEY"
},
"danskassistent_AWS_IAM": {
"ApiUrl": "https://xxxxx.appsync-api.eu-central-1.amazonaws.com/graphql",
"Region": "eu-central-1",
"AuthMode": "AWS_IAM",
"ClientDatabasePrefix": "danskassistent_AWS_IAM"
}
},
"CredentialsProvider": {
"CognitoIdentity": {
"Default": {
"PoolId": "xxxxx",
"Region": "eu-central-1"
}
}
},
"CognitoUserPool": {
"Default": {
"PoolId": "xxxxx",
"AppClientId": "xxxxx",
"Region": "eu-central-1"
}
},
"Auth": {
"Default": {
"OAuth": {
"WebDomain": "xxxxx.auth.eu-central-1.amazoncognito.com",
"AppClientId": "xxxxx",
"SignInRedirectURI": "myapp://",
"SignOutRedirectURI": "myapp://",
"Scopes": [
"phone",
"email",
"openid",
"profile",
"aws.cognito.signin.user.admin"
]
},
"authenticationFlowType": "USER_SRP_AUTH",
"mfaConfiguration": "OFF",
"mfaTypes": [
"SMS"
],
"passwordProtectionSettings": {
"passwordPolicyMinLength": 8,
"passwordPolicyCharacters": []
},
"signupAttributes": [
"EMAIL"
],
"socialProviders": [
"GOOGLE",
"APPLE"
],
"usernameAttributes": [
"EMAIL"
],
"verificationMechanisms": [
"EMAIL"
]
}
}
}
}
}
}
GraphQL Schema
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: