Callback URL with a hashbang results in 'is not a valid URL' error

[pulsar]

Under Manage My Apps we provide a Callback URL that needs to contain a hashbang. Unfortunately this results in an error that our url is 'is not a valid URL'.

Is there a way to workaround this? Why are hashbangs not allowed?

[ibahdanau]

Please check out this post.

http://stackoverflow.com/questions/2286402/url-fragment-and-302-redirects

The workaround I'd say - not to use hashbangs:). Use url that does not have hashbangs and once Fitbit forwards user to your server you can try to write custom code that will be doing redirect to the url with hash tag that you need. 

[JeremiahFitbit]

Thank you for the bug report. We have filed this internally and will fix. I don't have an estimated date when it will be fixed.

Unfortunately, the only interim solution is to not use a hashbang in your callback URL.

[ShaneFitbit · Accepted solution]

Hi pulsar,

The bug should be fixed now. Thanks for bringing this to our attention, and apologies for the delay!

-Shane