#61

I ran into this problem today. The fix, for me, was to use something other than Chrome. Safari did the trick.

#62

Thank you - is this the solution to the problem I pasted above?

#63

I believe it is. There is some Chrome browser incompatibility with that aspect of the site. Safari and Firefox accept changes to this form field.

#64

@AllstateBev & @generaluidev - my dev says “The only big problem is how to add the domain/url.
I already tried messing up with the app name or any other browser, still no luck”. Please guide further how to solve this. Thanks.

#65

one like startlight

#66

Error
Validation failed: example is already taken for Name

This is the error when i try to create the app

#67

Can anyone please give me a solution for this… Im frustrated with this :frowning:

#68

have you tried specifying a different name to “example” which is more descriptive?

#69

Thanks, it work for me

#70

Have tried Chrome and Internet Explorer, changing project name, project description, using many valid URLs but I still get this issue. How can I overcome it?

#71

You were dead ON! I checked and sure enough there was a space in the front of the http://
They need to take your response and push it up to the top as a the resolution for 99.9% causes of this error message.

Thank you!

1 Like
#72

For all those who are having issues with using http://localhost:8080, use http://127.0.0.1:8080 instead.
Worked for me ! :slight_smile:

P.S I have used port 8080. You can have something different.

Cheers.

#73

im working on localhost:6448 port and im facing the same issue.can u please tell me what website name and calll back url i should provide

#74

It is most definitely a Chrome browser issue!
After multiple failed attempts I opened up Firefox and managed to register my app name in 30 seconds using the exact some details in all the fields that Chrome kept returning an error.
It should work just like this: http://iag.me/socialmedia/how-to-create-a-twitter-app-in-8-easy-steps/

#75

Hey
I was confused … but the problem with me
that i have added a space before the url
so the url should be "http://example.com"
not " http://example.com"
and this worked for me

1 Like
#76

EVERYONE I FIGURED OUT THE REAL PROBLEM. Everyone is confused on this thread because people didn’t realize what the real problem was. It’s not a browser issue, localhost, or anything else. First of all, Twitter could save a MASSIVE amount of confusion by simply showing you WHICH field is having an error, which they don’t, and that’s why the confusion.

Yes, it requires the URL be prepended with HTTP:// or HTTPS://, but what was not clear is that BOTH the website AND the call back url needed this. Everyone was focusing on the call back url, including me, and kept on trying different browsers (again me included) and still no luck. And the whole time it wasn’t the call back url that had the problem, it was my website.

So Twitter does a horrible job on telling you WHERE the problem is. And they should really fix that. Everyone including me thought it was the call back url when it was my website.

SOLUTION: PUT HTTP:// or HTTPS:// for both website AND callback and it will be fine!!!

#77

The following works:
you can’t use http://localhost:3000, it’s not an IP address
use http://127.0.0.1:3000/users/auth/twitter/callback
and also use http://domainname.com in your website field, no caps allowed in your website URL
Twitter needs to do a better job on their error messages.
It’s not browser dependent. I tried chrome, safari, firefox

#79