12-15-2018 09:18
12-15-2018 09:18
I've been using http://localhost:PORT/callback as my callback url for testing, but when I try to edit it to http://somehost:PORT/callback for deployment, I'm seeing an error message saying HTTPS is required.
However when I hover beside the field for callback url, the tooltip text says HTTPS is recommended but not required. Am I missing something?
12-17-2018 15:24
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-17-2018 15:24
Hi @someuser101. We have restricted the callback URL to support HTTPS only. The information in the tooltip is outdated. Thank you for pointing that out.
Best Answer01-20-2019 22:25
01-20-2019 22:25
Hi @Gordon-C. Has callback URL been restricted to support HTTPS only across all platforms? I have some users on iOS that are experiencing 404 errors on authorization, and the callback URL is currently just a standard iOS callback URL (myappscheme://). However, it still works for a number of users - I'm not sure why it would work for some and not all. Thanks in advance for the help
Best Answer01-22-2019 10:17
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.
01-22-2019 10:17
Hi @jonbee75,
The callback URL for web apps should be HTTPS. However, I believe your problem is related to something else. Your callback URL needs to be an absolute URL, meaning it needs to look like myappscheme://callback.
Gordon
Best Answer