We had a VMWare DLT running DAML Connect 1.11.1. We previously had a DAML application, with daml.yaml:
sdk-version: 1.11.1 name: daml-app source: daml parties: - Alice - Bob - Charlie - David version: 0.0.2 dependencies: - daml-prim - daml-stdlib codegen: java: package-prefix: xx.xx.xx.xx output-directory: ../src/generated/java verbosity: 2
We had a workflow, where if we attempted to fetch a contract which did not exist, it would return an error as below:
io.grpc.StatusRuntimeException: INVALID_ARGUMENT: Command interpretation error in LF-DAMLe: dependency error: couldn't find contract ContractId(00e86b0cebaf72460abdb36ac73f2e32cdbd253652420949b8b6671360d373af2a). Details: N/A.
We then upgraded our DLT platform to DAML Connect 1.14. We kept the same application, with the same daml.yaml file. However, the same workflow resulted in error:
io.grpc.StatusRuntimeException: ABORTED: Command interpretation error in LF-DAMLe: Contract could not be found with id ContractId(00c89a27a7d5af4d8d98ef126354b1b1bba4067a0de943445481a6dabd4ddd4596). Details: N/A.
This change was not mentioned in the release notes and we came across it by chance as it broke one of our backend systems. We also attempted to set the build-options to force target 1.11, however, we still received the new error code.
I was wondering whether we can expect more changes of this nature or this a bug as it causes us a lot of problems with backwards compatibility.