You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2024. It is now read-only.
The above curl command gives this error: {"statusCode":409,"error":"Conflict","message":"More than one address for the same (payment_network, environment) tuple was provided"}
In order to create the verified PayID, the PaymentInformation must be removed from the addresses array.
Context
This might not be an issue if the intended behavior is to make sure a verified address isn't also in addresses, but there should be consistency between the CLI tool and the reference implementation.
Potential Solution
We should have a discussion about whether this behavior is intended and whether the CLI tool or the reference implementation needs to be changed so that they match.
Steps to Reproduce
See above
Environment
Node version:
NPM version:
Operating System and version:
PayID server version:
PayID Version header (if applicable):
Screenshots
If applicable, add screenshots to help explain your problem.
Bonus
Are you willing to submit a pull request to fix this bug?
Yes
The text was updated successfully, but these errors were encountered:
Expected Behavior
The CLI tool outputs this after signing with an identity key:
So the corresponding Admin API request to create the PayID should be:
Actual Behavior
The above curl command gives this error:
{"statusCode":409,"error":"Conflict","message":"More than one address for the same (payment_network, environment) tuple was provided"}
In order to create the verified PayID, the PaymentInformation must be removed from the addresses array.
Context
This might not be an issue if the intended behavior is to make sure a verified address isn't also in
addresses
, but there should be consistency between the CLI tool and the reference implementation.Potential Solution
We should have a discussion about whether this behavior is intended and whether the CLI tool or the reference implementation needs to be changed so that they match.
Steps to Reproduce
See above
Environment
Screenshots
If applicable, add screenshots to help explain your problem.
Bonus
Are you willing to submit a pull request to fix this bug?
Yes
The text was updated successfully, but these errors were encountered: