Skip to content
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

Use existence of API config to trigger sync start #177

Closed
palpatim opened this issue Nov 27, 2019 · 1 comment
Closed

Use existence of API config to trigger sync start #177

palpatim opened this issue Nov 27, 2019 · 1 comment
Labels
api Issues related to the API category datastore Issues related to the DataStore category feature-request Request a new feature

Comments

@palpatim
Copy link
Member

Currently we're using the existence of syncable models to start syncing; instead use the Android method of detecting whether an API is configured

@palpatim palpatim added api Issues related to the API category datastore Issues related to the DataStore category enhancement labels Jan 13, 2020
@drochetti drochetti removed the P0 label Jun 24, 2020
@drochetti
Copy link
Contributor

This was fixed at some point before GA. Currently DataStore starts syncing based on the presence of a configured Amplify.API.

@lawmicha lawmicha added feature-request Request a new feature and removed enhancement labels Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Issues related to the API category datastore Issues related to the DataStore category feature-request Request a new feature
Projects
None yet
Development

No branches or pull requests

3 participants