Dan Rivett

I'm also very interested in this because I'm attempting to run e2e tests for an iOS app that integrates with an AWS AppSync backend (incidentally using @edvinasbartkus's great guide [here](https://dev.to/edvinasbartkus/running-react-native-detox-tests-for-ios-and-android-on-github-actions-2ekn)...

Also for reference (at least for others like myself who wasn't aware): - Here is the [GitHub documentation](https://help.github.com/en/actions/building-actions/about-actions#types-of-actions) describing different types of GitHub Action implementations. - And specifically the documentation...

Key here is I needed the date not only to be generated with millisecond precision, but also to be generated in the UTC timezone, not my local timezone. I couldn't...

Bumping this as just installed your plugin on my new machine and wondered why it wasn't working - I forgot I installed my fork last time. Be great to get...

@iartemiev Thanks for your quick reply and explanation, apologies for my delayed response. It wasn't due to a lack of importance or attention on my part, it was actually the...

The solution we implemented is a standard replication pattern where for our Timesheet scenario a worker would create a timesheet and own it themselves, and then a backend lambda would...

We also have run into this limitation as we use Amplify DataStore which heavily relies on AppSync Subscriptions and have have some quite heavily denormalized types which can result in...

@renebrandel this may be an AppSync limitation that you can encourage a fix for from your end as if a AppSync notifies DataStore when a subscription update is either not...

@jpignata returning an error would be great as long as the error identifies which data couldn't be returned (may be simply enough to return the input parameters to the subscription...

Thanks John, no idea, as it's managed through Amplify DataStore so largely opaque to us. We're using `"@aws-amplify/datastore": "^3.4.7"` which isn't old so can't imagine it's using MQTT, but I...