Fabric automatically generates Twitter API keys for you to use when you use Twitter or Digits in your app. These keys are provisioned properly to access all the features from Fabric’s TwitterKit.

Your users see the provisioned name when they manage access to their account on Twitter’s settings, or when logging in via an oAuth webview. Now you can edit the properties of these Twitter keys on your Twitter dashboard at fabric.io. You can easily change your application’s name on Twitter, description, website, callback urls, or change your token to be read-only.

I’m a bit confused by this. Does this replace having to create the app at apps.twitter.com? I have tried creating and using both consumer key/secrets from both places but I get error code 400 regardless.

You can continue to use apps.twitter.com to create your app keys if you choose - and then put them into your Fabric app. Alternatively, you can let Fabric generate them for you, and then manage the app at fabric.io.

For all still having problems with ‘refreshing’ this app info after changing it,
try to ‘force’ reconfigure TwitterKit via Fabric App (by clicking on ‘installed’ button and going over setup again),
also check your data for consumerKey and consumerSecret inside Info.plist.