New: Edit your Fabric generated Twitter keys at fabric.io


#1

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.

Try it today by logging into your Twitter Dashboard at fabric.io

(Changes may take up to an hour to take effect. )


#2

Awesome. Thanks for listening and making the changes.


#3

#5

Is there a way to upload a picture for this app? It looks pretty shady not to have one.


#6

We are still seeing old info (self-generated - e.g. “…by Fabric”) for our app after few days and as there’s no way to change the pic for the app it looks shady.


#7

I have the same problem. I changed the name of the app at farbric.io several days ago, but I am still seeing the name “Authorize Created by Fabric for …” on the authorization web page.


#8

I have the same problem too. I changed Application name on Twitter dashboard few days ago, but "Created by Fabric for … on ios* is still shown as a application name on oAuth WebView.

How can I change application name shown on oAuth WebView?


#9

Same problem.
Is there any way to turn off this registration page and redirect the user to settings (in case of ios) instead?


#11

Siz kime şekil yapıyosunuz!


#12

This is still not working. Are there any updates on this issue?


#13

The same problem with the app name.


#14

Seeing the same issue. Despite changing details on Fabric.io over a week ago, the default details are still showing.


#15

I am also seeing the same problem. Could you please mail me the steps I need to do for getting this fixed…my mail id is robinverma (at) gmail (dot) com


#16

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.


#17

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.


#18

I am stuck in the onboarding process so cannot access this dashboard.

Is it possible to use Twitter without fabric please as it requires that app to be open which breaks the build if you have multiple engineers working on it who don’t need fabric installed.

Essentially we will have consider not using Twitter login as this new process is invasive and cumbersome for large teams.


#20

#21

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.


#22

Yes. You can change the icon of the app in settings. Not in dashboard. But not every image matches. I haven’t found the requirements, but one image is good and other is not.


#23

I had the same problem until recreated app in Fabric.