-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistency between listWebhook() function and get request directly from Postman #117
Comments
Edit: I tried fetching it directly and it returned the list of webhooks properly including id #25098. Is there anything wrong with the way I was calling listWebhooks? Code:
Logs:
|
Hey @antoineross, Make sure the API keys are identical and correspond to the same mode (Test or Live). Also, check if the page, layout, or fetch call are cached in Next.js (based on your configuration). In our example we have added: See Next.js docs on this. Edit: I was able to replicate this is on my side. Add |
I found that it was a caching issue on my side as well. Deleting /.next fixed it. Will close this now, thank you for validating the issue. I appreciate it. |
Hi, so I was using the repository: https://github.com/lmsqueezy/nextjs-billing/ and specifically in the code from file: https://github.com/lmsqueezy/nextjs-billing/blob/main/src/app/actions.ts, where we call listWebhooks() I get a different response vs getting the request directly using Postman.
I tested this because I was trying to look for the webhook I created with id #25098 (using the same file from nextjs-billing repo). If you will look at the logs, you will notice that #24749 exists on the logs for both listWebhooks() and using Postman, but the problem lies in #25098 existing in Postman but not in listWebhooks().
To give you more context here is the code I am using:
Code:
I get the following results from logs:
I have also tried removing the filter but still nothing:
But when I call it directly using Postman, I get a different response:
I will also attach a full response here:
The text was updated successfully, but these errors were encountered: