Adam Rodger

@mefellows this looks like an FFI error similar to the one I found a while ago about falling to parse certs. It looks like it still tries to load the...

The defect is in a different library, not in PactNet. Pull requests are gratefully expected if this is urgent. Alternatively your quickest option will be to identify and remove and...

I was just trying to remember where that sample app was 😂 I thought the native TLS lib had changed so that you can handle parsing errors in user code,...

That looks more like the certificate of the broker you're using is invalid to me. I'm not sure if you're using a self hosted broker or Pactflow though.

Yeah so that means that the host where you're running the tests doesn't trust the cert being used by the broker. I can't really help you with that because that...

You can see here that the call is awaited immediately upon being invoked: https://github.com/pact-foundation/pact-net/blob/master/src/PactNet/Verifier/Messaging/MessageScenarioBuilder.cs#L63 And then it sets the resultant value as a sync factory internally. We know that's definitely...

I'm not sure that's the case. Given the method is called and awaited immediately then the value must be available at that point: ```csharp public async Task WithContentAsync(Func factory) {...

Ah ok I see the confusion - the API isn't intended to be a callback that's executed for each interaction during the verification. It's a one-time setup to create some...

Yeah that sounds like interop problems would be the first thing to check. We should definitely have some tests using non-ASCII characters and we don't, so that's the first thing...

I've tested this out locally and it breaks pretty badly with non-ASCII characters in things like consumer/provider names, interaction names, provider states, etc. It generally seems to fail everywhere because...