We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Similar to #312 except a bit more annoying this time. Once initialized, the secure API does not accept ID as string.
{ "id":"3", "jsonrpc":"2.0", "method":"encrypted_request_v3", "params":{ "nonce":"2994319f73303015805b22c3", "body_enc":"M1X8zvf0MTjJ8uYkEOWlxKcRvz16g+PtiKNdttYddlMapOzGi8gV7yJrsOYdDkaLhVP3Y3o8LTGuVW56EpV+s8Tjgxy9DWoPIiW1vMm5V0ITvXX2enZVgswmkvNjnkhjTB1tydpv" } } { "error": { "code": -32002, "message": "Encrypted request format error: invalid type: string \"3\", expected u32" }, "id": 1, "jsonrpc": "2.0" }
The text was updated successfully, but these errors were encountered:
Preparing a PR for that one.
Sorry, something went wrong.
Fixed via PR
No branches or pull requests
Similar to #312 except a bit more annoying this time.
Once initialized, the secure API does not accept ID as string.
The text was updated successfully, but these errors were encountered: