Open ziyaaktas opened 2 months ago
Have you checked middleware.ts
? I had the same issue locally. Then I figured out middleware.ts
was bypassing all routes including api/inngest
. So, I added api/inngest
to the matcher.
middleware.ts
// AS-IS
import { auth } from "@providers/auth";
export default auth((req) => { // some logic like authentication });
export const config = { matcher: ["/((?!_next|api/auth|logo.svg|favicon.ico).*)"], };
```typescript
// TO-BE
import { auth } from "@providers/auth";
export default auth((req) => {
// some logic like authentication
});
export const config = {
matcher: ["/((?!_next|api/auth|api/inngest|logo.svg|favicon.ico).*)"],
};
Describe the bug I have been going through the guides just to try out the ingest product. However I couldn't pass the syncing apps part.
To Reproduce Go through the https://www.inngest.com/docs/quick-start tutorial.
Expected behavior Local server syncs with nextjs
Code snippets / Logs / Screenshots route.ts
When I ping localhost:3000/api/inngest, I get this response {"message":"Inngest endpoint configured correctly.","hasEventKey":false,"hasSigningKey":false,"functionsFound":1,"mode":{"type":"dev","isExplicit":true}}
System info (please complete the following information):
Additional context Add any other context about the problem here.