@katejaiheelee the problem still exists with TwitterKit 3.0.4 and Twitter app 7.4

To fix it properly each app needs to specify a unique app URL scheme so that the Twitter app will be able to forward login data back to the correct one. A simple (and backward compatible solution) is to support URL scheme suffix. This way application 1 and 2 have different URL schemes and this problem will never happen again.
Facebook SDK does the same, so it’s a solid solution.

Hi there,
we have an online platform that is used by several iOS apps. All of them can sign in the user authenticated via Twitter. This requires using the same (twitter) consumer key and secret across all iOS apps. This creates a problem now that the consumer key is added to the Info.plist to redirect the user from the Twitter app back to the calling app. We can have multiple apps installed on the phone with the same URL scheme.
Is it possible to differenciate the URL scheme in any way? Face…

Please take this in consideration “quickly”. With iOS11 there is no other way of authenticate user that using TwitterKit and now it’s clearly broken.