Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Non-syncable models prevent SyncEngine start

See original GitHub issue

Describe the bug Non-syncable models prevent SyncEngine start. Sync Queries are NOT generated for Non-Syncable Models, but the syncQueriesObservable method still tries to wait on them.

This is an unusual error because Models in the generated schema (src/models/schema.js) have the property syncable set to true by default.

To Reproduce Steps to reproduce the behavior:

Init Amplify, add GQL, enable DataStore, add Codegen.
Create at least 2 Models in your schema.
Modify the generated schema (src/models/schema.js) and set one of the models to syncable: false
Push
Run your app.
Although the DataStore reports “Realtime ready”, it never goes online and nothing gets synced.

Expected behavior Skip non-syncable models.

Code Snippet I think the problem is here: https://github.com/aws-amplify/amplify-js/blob/main/packages/datastore/src/sync/index.ts#L380-L401

And the solution might be to filter syncable models.