#joshuadoore

1 messages · Page 1 of 1 (latest)

sour folioBOT
cloud bone
#

Hi there 👋 are you receiving an error indicating a matching signature could not be found?

That is typically encountered for one of two reasons:

  1. The signing secret does not match the secret of the endpoint being used. Each endpoint generates a unique signing secret, so you will need to update that value if you're working with a new endpoint.

  2. The contents of the request body that you're providing to constructEvent do match the exact contents of the body we sent. Our current implementation is very sensitive and will fail due to any changes in the request body, including altering the amount of whitespace.

I'm not too familiar with next/server specifically, so I'm not sure how to ensure you're getting the raw unaltered request body in that environment, though I would have expected your buffer approach to work.