From 5988182145a9229451cc8e1a8fe64aef1069b900 Mon Sep 17 00:00:00 2001 From: Elliot Lee Date: Thu, 21 May 2020 17:44:18 -0700 Subject: [PATCH 1/2] Submit - document the `notSupported` error Per https://github.com/ripple/rippled/pull/2657 some rippled servers no longer support signing, so Sign-and-Submit mode has a possible error of `notSupported`. The change was introduced in rippled version 1.1.0 and merged via: https://github.com/ripple/rippled/commit/38c3a46a337916216a1e3ad481229fe87e07d542 The error looks like: "name": "notSupported", "message": "Signing is not supported by this server.", "code": 75, ... --- .../public-rippled-methods/transaction-methods/submit.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md b/content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md index cb8587d2ec..fe849e1860 100644 --- a/content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md +++ b/content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md @@ -320,6 +320,7 @@ The response follows the [standard format][], with a successful result containin * `invalidTransaction` - The transaction is malformed or otherwise invalid. * `noPath` - The transaction did not include paths, and the server was unable to find a path by which this payment can occur. (Sign-and-Submit mode only) * `tooBusy` - The transaction did not include paths, but the server is too busy to do pathfinding right now. Does not occur if you are connected as an admin. (Sign-and-Submit mode only) +* `notSupported` - Signing is not supported by this server. (Sign-and-Submit mode only) From c4b61347e27aebccda844c7267cc69744bdb7c0d Mon Sep 17 00:00:00 2001 From: Rome Reginelli Date: Tue, 26 May 2020 16:11:42 -0700 Subject: [PATCH 2/2] submit: signing notSupported edits add relevant links --- .../public-rippled-methods/transaction-methods/submit.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md b/content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md index fe849e1860..de23ce29d1 100644 --- a/content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md +++ b/content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md @@ -320,7 +320,7 @@ The response follows the [standard format][], with a successful result containin * `invalidTransaction` - The transaction is malformed or otherwise invalid. * `noPath` - The transaction did not include paths, and the server was unable to find a path by which this payment can occur. (Sign-and-Submit mode only) * `tooBusy` - The transaction did not include paths, but the server is too busy to do pathfinding right now. Does not occur if you are connected as an admin. (Sign-and-Submit mode only) -* `notSupported` - Signing is not supported by this server. (Sign-and-Submit mode only) +* `notSupported` - Signing is not supported by this server (Sign-and-Submit mode only.) If you are the server admin, you can still access signing when connected [as an admin](admin-rippled-methods.html), or you could [enable public signing](enable-public-signing.html). [New in: rippled 1.1.0][]