11-17-2022 17:54
11-17-2022 17:54
Greetings folks! I'm writing an app that requires a webhook to be set up. I am using `ngrok` locally to create a tunnel to my machine, which is running a local node.js app with express.
I created a new Subscriber, wrote the code laid out in https://dev.fitbit.com/build/reference/web-api/developer-guide/using-subscriptions/#Verifying-a-Subs... and clicked the "verify" button. On my local web server I am seeing two requests come through - I respond to the one with the correct verification code with a 204 and no content, and I can see the 404 coming back for the verification code that doesn't match. Everything on my end appears to be peachy 🙂
However .... nothing updates or changes on the web UI for the app at https://dev.fitbit.com/apps/details/<redacted>. The Verify button just sits there.... pink, mocking me. Is there any way for me to debug this? The only thing I can think of at this stage is that ngrok is somehow creating problems. Thank you!
11-18-2022 06:51
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
11-18-2022 06:51
Hi @justinblat
I need to collect some information from you to conduct some research on my side. I will reach out to you directly.
Gordon
Best Answer11-19-2022 12:02
11-19-2022 12:02
Ngrok has worked for us no problems. Must be something else in your setup.
Best Answer12-12-2022 12:39
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
12-12-2022 12:39
To circle back on this problem, the application sent us the 204 response but it was missing the 404 response.
Best Answer