Adam Kecskes comments

Results 6 comments of


                                            Adam Kecskes

Getting an "Invalid request payload" error with `addNewIssue` and an Atlassian Document Format payload

I pulled this code down and tinkered with things to find that with `apiVersion` 2 and a _non-stringified_ options payload, all works well. Either stringifying or `apiVersion` 3 (which requires...

Getting an "Invalid request payload" error with `addNewIssue` and an Atlassian Document Format payload

Success! I'm not clear on what I was doing wrong in the past that originally prompted me to make this post, but I suspect it had to do with a...

Getting an "Invalid request payload" error with `addNewIssue` and an Atlassian Document Format payload

I know this asking a bit beyond what is expected of an open source project, but since it was a red herring in my search. perhaps you can clear something...

Failed to verify accountId. [-32700] Parse error: Failed parsing args: missing field `account_id`

I'm experiencing the same issue. Is there a way/need to generate the keys for `.near-credentials/testnet/*.json` such that it matches the `public_key` param that is being passed up to the browser?...

Failed to verify accountId. [-32700] Parse error: Failed parsing args: missing field `account_id`

According to this site: https://www.near-sdk.io/zero-to-hero/basics/set-up-skeleton, > When you typed near login, NEAR CLI generated a key pair: a private and public key. It kept the private key tucked away in...

Failed to verify accountId. [-32700] Parse error: Failed parsing args: missing field `account_id`

I looked into the near-cli source code and found that there was a [callback using port 5000](https://github.com/near/near-cli/blob/2c21e2e2a80bff4506362f82b705bdc4de4639a4/index.js#L131). My Mac (Monterey 12.3.1) was using port 5000 already, which I couldn't kill...