there is a simlar unresolved github issue here: https://github.com/aws-amplify/amplify-studio/issues/1111
#Relationship errors after big update?
rustic totem
rustic totem
this documentation is not helpful: https://docs.amplify.aws/react/build-a-backend/data/data-modeling/relationships/
With Amplify Data Construct @aws-amplify/[email protected], an improvement was made to how relational field data is handled in subscriptions when different authorization rules apply to related models in a schema. The improvement redacts the values for the relational fields, displaying them as null or empty, to prevent unauthorized access to relational data.
This redaction occurs whenever it cannot be determined that the child model will be protected by the same permissions as the parent model.
Because subscriptions are tied to mutations and the selection set provided in the result of a mutation is then passed through to the subscription, relational fields in the result of mutations must be redacted.
If an authorized end-user needs access to the redacted relational fields, they should perform a query to read the relational data.
Additionally, subscriptions will inherit related authorization when relational fields are set as required. To better protect relational data, consider modifying the schema to use optional relational fields.
nothing makes me more upset then telling me something won't work but then doesn't provide a solution. i don't care if my fields are redacted but it shouldn't throw errors like the aboe OR how about giving us information on how to navigate this change so we're not sitting here dumbfounded on how to fix it.
this also doesn't appear to just apply to "subscriptions" as mine is a simple create mutation facing the same issues outlined in the docs.