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
A credential definition can go into an un-publishable state, if it ever fails to be written to the ledger. This is because it is only written to the ledger if it does not already exist in the wallet ... and it will remain in the wallet if ledger publishing fails for whatever reason ...
Creating a new cred def with POST /v1/definitions/credentials may therefore result in a bad request error:
400: Credential definition `cred_def_id` is in wallet `wallet_name` but not on ledger `ledger_name`
The only current workaround is to try creating a different cred def, with a new tag.
A simple solution would be to contribute some logic to allow the "if not on ledger and exists in wallet, raise Exception" step to be bypassed, such that publishing to ledger can be retried.
The text was updated successfully, but these errors were encountered:
A credential definition can go into an un-publishable state, if it ever fails to be written to the ledger. This is because it is only written to the ledger if it does not already exist in the wallet ... and it will remain in the wallet if ledger publishing fails for whatever reason ...
Creating a new cred def with
POST /v1/definitions/credentials
may therefore result in a bad request error:The only current workaround is to try creating a different cred def, with a new tag.
This is a known bug in ACA-Py:
A simple solution would be to contribute some logic to allow the "if not on ledger and exists in wallet, raise Exception" step to be bypassed, such that publishing to ledger can be retried.
The text was updated successfully, but these errors were encountered: