Its working fine now :)
On Aug 7, 3:50 am, Dana Contreras <d...@twitter.com> wrote: > Hi Steve, > > Our OAuth implementation is very strict about host names and will not > authorize callbacks unless the host name matches exactly. In your > case, the www subdomain is the difference. > > You can make your @Anywhere app work on both host names by adding > mymobileplanet.co.uk (without the www) to your list of authorized > domains. Go tohttp://dev.twitter.com/apps, click on the name of your > @Anywhere app, and then click on Manage Domains in the right sidebar. > Enter mymobileplanet.co.uk into the form field and click Authorize. > > > > On Fri, Aug 6, 2010 at 10:56 AM, Steve <atif-nas...@hotmail.com> wrote: > > I have implemented @Anywhere on a web-page. I have registered an app > > with Twitter and inserted the API key in the head section and both > > modules in the body section of my page. > > > I am getting the following error: > > > The provided callback urlhttp://mymobileplanet.co.uk/iPhone.htmlis > > not authorized for the client registered to 'http:// > >www.mymobileplanet.co.uk'. > > > I have tried several methods to somehow make it work but all in vain. > > > I would appreciate if someone can visit my pages and see what the > > problem is or guide me how I can make it work. > > -- > Dana Contreras > Twitter Platform Teamhttp://twitter.com/DanaDanger
