Hi team, We are facing an issue with some contract...
# pact-broker
i
Hi team, We are facing an issue with some contracts not resolving as expected. We have a bidirectional contract setup, with consumers implemented in JavaScript and Java, and the provider code(developed in Java) has published the API specification. During verification, the contract tests are passing, but Pact indicates that the provider is not compatible with the consumer contract. Additionally, we are encountering the following error message:
Copy code
{
  "error": {
    "message": "Cannot read properties of undefined (reading 'type')"
  }
}
Could you please assist us in diagnosing and resolving this issue? Thank you! FYI: @Luis Eduardo Camilo
m
If you’re using Bi-directional, then this comparison check happens in PactFlow. Could you please share the pact and/or OAS file?
During verification, the contract tests are passing,
which verification?
i
Hey Matt, we cannot share the files in this thread because the data is sensitive for our company. Is there any channel or email where we can send the files?
which verification?
The tests are passing, but is informing an incompatibility between the services.
m
Is the OAS valid? Try validating it in editor.swagger.io etc. and see if anything shows up. That’s the likely cause
Alternatively, create a repro that doesn’t use your company IP
(howtorepro)
i
@Matt (pactflow.io / pact-js / pact-go) Thank you for the support. We discovered that the issue was the lib that we were using to generate the api specification.