This was reported 3/15 by another user, then resolved as "not an issue" with the request to be moved to a discussion.
It is still a problem. I have attempted to create a new application with multiple variations of valid, fully qualified urls -- even going so far as to attempt "http://google.com" -- and it is still rejected. If Google is not a valid website, I am not sure what qualifies! :)
Replies
Thanks for the report, Laura.
So we can understand the exact specifics here -- can you retrace your steps:
You go to dev.twitter.com/apps you click on create an app... what exact data do you put in both the Website and Callback URL fields? (Both require explicit URLs, but you can leave callback URL blank). The website field is required.
Let's say i have these filled in, what's wrong, why not a valid URL?
app name: sp1n3.tweetz
WebSite: http://sp1n3.com/
CallBack URL: sp1n3:/// (also tried sp1n3://callback, sp1n3:///callback)
We will not accept non-HTTP or non-HTTPS URLs on the form on dev.twitter.com -- you could use such custom URI schemes dynamically on the oauth/request_token step of OAuth, provided you place a HTTP or HTTPS based placeholder in this field.
I've tried creating an app also and every single time, it tells me my URL isn't valid. I've left it blank, I've tried it with http:// and I've tried it without http://. How do I resolve this?
I am also having this issue with a regular http:// URL
HElp!
iam also getting the same problem
Please resolve it fastly
For people still having issues with this both your website and the callback url need "http://" in front. So this worked for me:
Website: http://example.com
Callback URL: http://example.com/auth/twitter/callback/
(the exact path is up to you)
Hope that helps!