[regression] Apollo Cache does not work with Actions

[giulianok]

I'm currently using Hasura 2.0.0-alpha9 with Apollo Client 3.3.15

All queries, mutations, and subscriptions are working as expected, except for queries to Actions.

I have the following Action:

The Backend responds with the correct JSON data.

Apollo Query (default) does not work, the data and error keys are empty (undefined).

This DOES not work

const { loading, data, error } = useQuery(QUERY)

This WORKS

const { loading, data, error } = useQuery(QUERY, {
    fetchPolicy: 'network-only',
  })

I'm assuming that Apollo makes the request, stores the data into the cache, reads from the cache, and then responds but it isn't being able to get the data from the cache.

I checked the Network tab and I'm getting the data

I'm also checked it using the fetch API

And this is from Apollo Chrome extension

It was working fine in Hasura 1.3.3 but stopped working on 2.0.0, is there something that changed in Actions?

[eviefp]

Hello @giulianok ! I am trying to replicate this bug.

Here's what I've done:

1. Created a new action identical to the one you provided.
2. Created a glitch.me project which simply returns some static data in the correct shape:

app.post('/hello', async (req, res) => {
  return res.json([{
    missingCode: "code-1",
    completed: false,
    reason: "reason-1"
  },{
    missingCode: "code-2",
    completed: true
  }])
});

3. Ran this query:

query MyQuery {
  accountStatus {
    __typename
    completed
    missingCode
    reason
  }
}

And the result I am getting is:

{
  "data": {
    "accountStatus": [
      {
        "__typename": "AccountStatus",
        "completed": false,
        "missingCode": "code-1",
        "reason": "reason-1"
      },
      {
        "__typename": "AccountStatus",
        "completed": true,
        "missingCode": "code-2"
      }
    ]
  }
}

I have tested this on 2.0.0-alpha.9.

The main point to notice here is that the __typename has the expected casing, whereas in your report, __typenames are "accountStatus" which looks wrong and may be the cause of the problem you are experiencing.

That being said, I am unable to reproduce a scenario where the __typename field has the wrong casing.

Could you try to create an easily reproducible case and share it with me? That would be very helpful in tracking down and fixing the problem you are experiencing.