-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
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
bug: invalid payload format: decoding failed: Incorrect base64 string #1564
Comments
Resolved by using base64 url encoding instead of standard base64 |
Can reproduce it with
And works with:
Looks like nwaku doesn't accept the padding
Unsure if a bug or feature. |
Re-opening as we agreed we should use standard base64 with padding for both encoding and decoding |
To understand what is wrong with the base64 encoding (in the JSON RPC context), I need to know the unencoded version of that "test vector". How did you encode that (using the |
As pointed out in the Discord discussion, PR #1572 fixed the issue. This can be marked as resolved. The fix will be included as part of the v0.16.0 release. |
Note that I did not encoded anything, I directly typed that. But can be easily replicated using https://www.base64encode.org/ |
Problem
JSON RPC API Does not accept valid base64 strings.
Impact
Cannot use v0.15.0 in the latest js-waku CI.
To reproduce
Do Json RPC Query:
Get an error:
Expected behavior
A message is sent with said payload
Screenshots/logs
Note taht https://base64.guru/converter/decode/hex is able to correctly decode the payload.
nwaku logs:
nwaku_Waku_Store_Generator.log
nwaku version/commit hash
v0.15.0
Additional context
The text was updated successfully, but these errors were encountered: