Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

Build for production

Hey All,

My customer is getting some pretty verbose errors (e.g. ASIHTTPRequestErrorDomain when twitter auth fails) and I'm wondering if there is a way to turn those off.

I seem to remember there used to be a way to build in a production mode vs building in development mode. Does that still exist?

I'm running Titanium Developer 1.2.1
Titanium SDK 1.4
iPhone SDK 4.0

— asked August 15th 2010 by Dustin Anderson
  • app
  • building
  • development
  • errors
  • production
0 Comments

3 Answers

  • What Twitter connection you are using for auth? Turning that message off wouldn't be idea, isn't it? How would they know if the login is good or bad?

    The reason i'm asking is i use the Twitter Xauth method in production apps, and it's catching all exceptions, including twitter overload. Knock on wood that it had not experienced the issue that you described.

    If you are using the oauth-adapter, then look into the oauth-adapter.js file; there you should be able to change the error text.

    — answered August 15th 2010 by Daniel Lim
    permalink
    0 Comments
  • Hey Daniel,

    We're using Twitter Xauth - I'm wondering what error you see when you put in an invalid username/password? Do you get different error messaging in production vs dev?

    Thanks.

    — answered August 15th 2010 by Dustin Anderson
    permalink
    0 Comments
  • ah, you are probably throwing the direct response error text instead of catching it then prompt a much user friendly one to user.

    Here's the free app implemented with twitter xauth. You can see the action there on article view.

    http://itunes.apple.com/us/app/slashgear/id367747163?mt=8

    — answered August 16th 2010 by Daniel Lim
    permalink
    0 Comments
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.