Sure, in applicationDidFinishLaunchingWithOptions we’ve got
Twitter.sharedInstance().start(withConsumerKey: "foo", consumerSecret: "bar"),
then in info.plist,
<key>CFBundleURLTypes</key>
<array>
<dict>
<key>CFBundleURLSchemes</key>
<array>
<string>twitterkit-foo</string>
</array>
</dict>
</array>
...
And then this for Fabric, not sure if the Kit config here is redundant or not now, we’ve migrated a few times.
<key>Fabric</key>
<dict>
<key>APIKey</key>
<string>baz</string>
<key>Kits</key>
<array>
<dict>
<key>KitInfo</key>
<dict>
<key>consumerKey</key>
<string>foo</string>
<key>consumerSecret</key>
<string>bar</string>
</dict>
<key>KitName</key>
<string>Twitter</string>
</dict>
</array>
</dict>
and lastly
<key>LSApplicationQueriesSchemes</key>
<array>
<string>twitter</string>
<string>twitterauth</string>
<string>itms-apps</string>
<string>fbauth2</string>
<string>fbapi</string>
<string>fb-messenger-api</string>
<string>fbshareextension</string>
</array>
and logging in with
Twitter.sharedInstance().logIn(completion: { session, error in
....
})