#Changes in Graphql on Berkeley ?

7 messages · Page 1 of 1 (latest)

blazing stream
#

I have been using this Graphql query for a long time without issues to check if the transaction has been included or has failed:

Endpoint: https://berkeley.graphql.minaexplorer.com

Payload:

{
 query:  {
     zkapp(query: {hash: "5JvBe5U8gNgsaEPSAf41ZnAUtcQNr7ZdTVNdfL1fJqkXiJeeSfAm"}) {
           blockHeight
           failureReason 
             failures
             index
           }  
       }
   },
 variables: null
}

But now it fails with this error (I know the transaction is included):

{
  "data": {
    "zkapp": null
  },
  "errors": [
    {
      "message": "reason=\"could not validate document: \\n\\tzkappCommand.accountUpdates.1.body.update.permissions.setVerificationKey: Invalid type. Expected: type: undefined, bsonType: [string,null], given: [object]\"; code=\"SchemaValidationFailedRead\"; untrusted=\"read not permitted\"; details=map[]",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "zkapp"
      ]
    }
  ]
}

So I assume something has changed since the new Berkeley release ?

Is there a solution for this ?

eager hamlet
#

Looks like the schema changed. I'll push a fix.

eager hamlet
#

Should be fixed now

blazing stream
blazing stream
#

Working ok now ! Thanks !

blazing stream
#

Mmm. Seems something is happening . Now fetchAccount fails with a known and funded account.

let hasAccount = await fetchAccount({ publicKey: deployer.publicKey });

returns

{
  statusCode: 200,
  statusText: "Cannot query field \"account\" on type \"Query\".",
}

where publicKey = 'B62qo1gZFRgGhsozfGeqHv9bbkACr2sHA7qRsf4r9Tadk3dHH3Fwwmy'