Repo ignored by maintainers

[JacobJT]

Widely used repo for major social platform doesn't receive updates or acknowledgment for plethora of issues

Expected behavior

Project maintainers respond to issues, fix bugs in a timely manner

Actual behavior

Issues go ignored and bugs that should be a simple fix remain in the production release

Steps to reproduce the behavior

Try to use the SDK and experience issues, report the issues.

[kevenbauke]

Regarding this topic :( They will stop the support for this SDK after October.

https://blog.twitter.com/developer/en_us/topics/tools/2018/discontinuing-support-for-twitter-kit-sdk.html

[JacobJT]

Ahh they took the ol' "We wanted to save money and let the community do it for us" approach with this and it hasn't worked out... That's a shame.

[NikKovIos]

According that news, we have two ways:

1. Create a petition and claim on twitter management with it. I don't think, that they don't have enough money to support the SDK development.
2. Write to them and beg to completely open the library. I mean, that the community would be able to approve pull requests.
3. Create another open source based on Twitter Kit in Swift.

Twitter Kit is necessary thing and needed to auth with twitter in a lot of apps. Their decision is VERY strange.

[bbookman]

What? This makes no sense at all

[bbookman]

Goodbye twitter login for my app in development now

[dafurman]

If you're just using this for login authentication, switch to using https://github.com/OAuthSwift/OAuthSwift. It's pretty easy to set up and allow for greater flexibility of OAuth services. No need to abandon Twitter's implementation of OAuth when it still works just fine.

[JacobJT]

Anybody have a simple, maintained, and not-soon-to-be-trashed solution if the only functionality you want is a social share button?

[pasevin]

@dafurman looks like OAuthSwift not hasn't been updated for months as well. You think it's solid?

[dafurman]

@pasevin Sure, at the end of the day OAuth is still supported by Twitter and that’s certainly not going anywhere, despite this repo not being maintained.
Plus, even if OAuthSwift were to have issues, all it does is remove the boilerplate from OAuth, which wouldn’t be hard to write yourself. There’re plenty of tutorials on it as well if necessary. I just suggest it to save a bit of time.

[evansobkowicz]

We've accepted the open PRs and included them in the recent 3.4.0 release. Please see the blog post referenced above for more info about the discontinuation of development on TwitterKit.

[JacobJT]

Thanks for the update. Will a new release be added to GitHub so we can review the changes that have been made?

Also, installation instructions could use a quick update:
https://github.com/twitter/twitter-kit-ios/wiki/Installation

Note: From v3.4.0 and higher, please make sure to remove all references to TwitterShareExtensionUI in your project settings if they are not already removed by Cocoapods. You may notice a TwitterShareExtensionUI resource bundle file in the "Build Phases" section of your project section, please remove this.

This is also an issue with Carthage, not doing so keeps the dozens of line of output complaining about duplicate files.

[rajul-arora]

@JacobJT I updated the Wiki with a similar note for carthage. Thanks for catching that!

[evansobkowicz]

Hi @JacobJT,

You can find the most recent GitHub release here: https://github.com/twitter/twitter-kit-ios/releases/tag/v3.4.0.