Hui Zhao

@Jordan-Nelson it looks like amplify-ios and amplify-android both are not going to change the original SQLite behavior. May need to align with native platforms use https://github.com/aws-amplify/amplify-flutter/issues/823#issuecomment-907541268 suggested workaround to achieve...

Both amplify-ios and amplify-android have decided to follow the convent of SQLite. Therefore, [the workaround](https://github.com/aws-amplify/amplify-flutter/issues/823#issuecomment-907541268) is needed to achieve what the issue described. Will update the integration tests using the...

OK, thanks for the feedback. I agree, it's better to make the abstraction not to be leaky (using DataStore has to know about SQLite). I'll see what we can do.

Hi all, amplify-android maintainers suggested [a workaround](https://github.com/aws-amplify/amplify-android/issues/1287#issuecomment-1132266263).

Hello @justkj7 sorry for the delayed response. I was trying to repro this issue you were experience. Could you let me know: * Is this still happening for you? *...

Hi @justkj7 I see the issue now. Looking at your schema for `Room` model ```graphql type Room @model @auth(rules: [{allow: public}]) { id: ID! @index(name: "roomIdOnCreatedAt", sortKeyFields: ["createdAt"], queryField: "roomIdOnCreatedAt")...

Hi @justkj7 sorry for the delayed response. This issue is very similar to https://github.com/aws-amplify/amplify-flutter/issues/306 which probably requires a fix in the transformer. I've reached out to [amplify-category-api](https://github.com/aws-amplify/amplify-category-api) maintainers for taking...

Hi @djsjr there is a [known issue](https://github.com/aws-amplify/amplify-android/issues/1690) in amplify-android that calling clear and start back to back may cause failures in the start call. As stop executes similar steps as...

Are you trying to reevaluate sync expression? Or just wanting to start DataStore after user signed in? If the latter, you don't need to invoke `stop()` prior calling `start()`. Please...

Hi @skim037 I think I actually encountered an issue in amplify-ios that prevents emitting the `ready` event under certain circumstances (I don't remember exactly how did I produce that error)....