Adding @auth directive breaks amplify push

Describe the bug Whenever I add @auth to one of my API models, I get a Cannot read property 'fields' of undefined exception when running amplify push. I do have Cognito authentication set up with my app and that works fine.

Amplify CLI Version 4.22.0

To Reproduce Adding @auth to this model gives me the error:

type UserAccount
  @model
  @key(
    name: "accountsByUser"
    fields: ["cognitoUserID"]
    queryField: "accountsByUser"
  )
  @auth(rules: [{ allow: owner }]) {
  id: ID!
  cognitoUserID: String!
  institutionName: String!
  institutionID: String!
  accessKey: String!
}

Expected behavior Expected @auth to work fine.

Screenshots

 Cannot read property 'fields' of undefined
An error occurred during the push operation: Cannot read property 'fields' of undefined

Desktop (please complete the following information):

• OS: Mac
• Node Version: 14.2

Additional context

[attilah]

@apiel51 I was not able to reproduce the issue with the provided schema, but thanks for the details that helped to locate the issue and you are right, the root cause is that subscription is not part of the schema element which can happen as in @bever1337 's case when schema is manually defined, now I’m making a fix for @bever1337 's case so it will add subscription member even if schema is manually defined but does not have the subscription operations type added.

@apiel51 could you provide some more details, do you have schema in your schema file defined? I want to make sure that we’re covering the grounds, but based on the stacktrace my fix will cover it. If after PR merge and release you can still reproduce it, feel free to reopen the issue.

@bever1337 to add custom operations to Query or Mutation or Subscription you don’t need to define the schema element in the schema, GraphQL compilation in the CLI will handle that. So this piece is not needed:

schema {
  query: Query
  mutation: Mutation
  subscription: Subscription
}

[github-actions[bot]]

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.