Open mhyassin opened 6 months ago
Hi @mhyassin, thanks for raising this issue and providing reproduction steps.
Can you confirm what version of the Amplify CLI you're using?
amplify --version
Also, if you can, please share you schema. Using a custom primary key might be enough to reproduce the issue but it might be helpful just in case there's something else we might be missing in our reproduction efforts.
Hi @chrisbonifacio,
I'm using amplify v12.12.0
and this is how the model looks like in the schema:
type User
@model
@auth(
rules: [
{
allow: owner
operations: [read, update, create, delete]
identityClaim: "username" # explicit use of username
ownerField: "user_name"
}
]
) {
user_name: String! @primaryKey
email: String!
firstname: String
lastname: String
# and other optional attrs
}
I get the same error with the following schema:
type UserObject @model @auth(rules: [{ allow: owner, ownerField: "id" }]) {
id: ID!
other: String
}
Seems to be an issue with the ownerfield being set to the primary key field.
Falling back to client-side filtering is really bad for our app. Is there estimated fix date for this error?
Is there any updated on when this might get fixed. Our schema relies on this working.
Before opening, please confirm:
JavaScript Framework
React Native
Amplify APIs
Authentication, GraphQL API, DataStore, Storage
Amplify Version
v6
Amplify Categories
No response
Backend
None
Environment information
Describe the bug
I'm getting this issue when adding
syncExpressions
to the Datastore configuration For more context see https://github.com/aws-amplify/amplify-category-api/issues/1796Expected behavior
The syncExpressions should run without any filtering errors
Reproduction steps
Code Snippet
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response