DataStore cannot delete `hasOne` relationships

Describe the bug DataStore cannot delete hasOne relationships. It breaks at IndexedDBAdapter.deleteTraverse when trying to find the recordToDelete of the HAS_ONE relationType.

Unhandled Runtime Error
NotFoundError: Failed to execute 'index' on 'IDBObjectStore': The specified index was not found.

To Reproduce

1. Init Amplify. Add GQL API. Enable DataStore.
2. Define the Schema below 👇
3. Generate Models. Push API.
4. Create Team then create Project with teamID.
5. Delete Project.
6. ERROR

Expected behavior The DataStore should correctly traverse the hasOne relationship to delete the Team record before deleting the Project record.

Code Snippet

Schema

type Project @model {
  id: ID!
  name: String
  teamID: ID!
  team: Team @connection(fields: ["teamID"])
}

type Team @model {
  id: ID!
  name: String!
}

Create Team then create Project with teamID.

    DataStore.save(
      new Team({ name: 'Team Name' })
    )
    .then(async ({ id: teamID }) => {
      DataStore.save(
        new Project({ teamID })
      )
    })

Delete Project.

DataStore.delete(Project, project.id)

What is Configured? Amplify 4.27.1 Simple Auth with Cognito GraphQL / Dynamo API DataStore NextJS app (irrelevant)

Additional context A couple of notes.

• From the implementation, looks like an index is expected for the hasOne relationship. https://github.com/aws-amplify/amplify-js/blob/main/packages/datastore/src/storage/adapter/indexeddb.ts#L676-L682

  case 'HAS_ONE':
    for await (const model of models) {
      const recordToDelete = <T>await this.db
        .transaction(storeName, 'readwrite')
        .objectStore(storeName)
        .index(index) // <-- 🤔
        .get(model.id);

• This goes counter to the docs where it states:

https://docs.amplify.aws/cli/graphql-transformer/directives#has-one A Has One @connection can only reference the primary index of a model (ie. it cannot specify a “keyName” as described below in the Has Many section).

• This is also where the error occurs, as index is undefined.

[iartemiev]

We’ve released a fix for this issue in aws-amplify@3.4.0.

For existing projects, you may need to set this CLI feature flag to true in ./amplify/cli.json. Afterward, make sure you have the latest version of @aws-amplify/cli, and run amplify codegen models.

If the model is getting generated correctly, you will see a new targetName property in the schema.js containing the field you’ve specified in @connection.

For example:

For this schema.graphql

type Project @model {
  id: ID!
  name: String
  teamID: ID!
  team: Team @connection(fields: ["teamID"])
}

type Team @model {
  id: ID!
  name: String!
}

You should see the following in /models/schema.js after you run amplify codegen models:

export const schema = {
  "models": {
    "Project": {
      "name": "Project",
        "fields": {
          ...,
          "teamID": {
            "name": "teamID",
            "isArray": false,
            "type": "ID",
            "isRequired": true,
            "attributes": []
          },
          "team": {
            "name": "team",
            "isArray": false,
            "type": {
              "model": "Team"
            },
            "isRequired": false,
            "attributes": [],
            "association": {
              "connectionType": "HAS_ONE",
              "associatedWith": "id",
              "targetName": "teamID" <----
            }
          }
          ...,

[TheMoums]

Ran into the same issue.

Any news on this @mauerbac ?