Chad Godsey

Same behavior on a Tinyhawk II STM32F411. Receiver connection unstable on 4.3.1, but good on 4.2.11.

Same error here NodeJS: 14.9.1 NPM: 8.6.0 homebridge-eufy: 0.4.0 node-eufy-api: 0.4.1

Seeing this on 2.28.0, 2.30.4 and 2.33.4 edit: to clarify, only reproducing the EXC_BAD_ACCESS when testing release builds.

Removing the auth rules for group field seems to be a workaround for now.

Of course. The LmShot and LmSession (which contains shots) are the models adding the groups field authorization rules. ``` """ User information is stored in the database to facilitate offline...

Thanks @harsh62! FYI this isn't currently a blocker for us. We transitioned away from this strategy for our current feature development. But we will likely revisit it in the future.

Hello @lawmicha, Yes, we sync only user owned data. So our sync expressions look like this in Swift: ```swift func syncExpressions() -> [DataStoreSyncExpression] { func userId() -> String { Amplify.Auth.getCurrentUser()?.userId...

Thanks @lawmicha! After signIn and Datastore stop/start, we get the .syncStarted event, but neither .modelSynced nor .ready are emitted. Our app does watch the .modelSynced events, but not in a...

This would be ideal. In our scenario, one of our most necessary items is the User table. This table doesn't have any dependencies but gets relegated to the end of...

Anything that can be done to help progress this? This is definitely a recurring issue for our users as they switch phones, receive app updates with new schemas, etc. The...