Hi,

I am trying to get the streaming api working and the code that I have so far is as below.

I have this method inside a singleton as suggested by @zntfdr here

when I call this singleton method from my VC I do not see any responses at all in the print. Is there something I am missing here?

I sometimes get this error message HTTP Status 420: Enhance Your Calm, Response: Exceeded connection limit for user which tells me that my connection is being established (or not). Do i need to put more tracker terms to see any significant streaming?

func start(){
        
        let tracker = ["#PSX2017"]
        guard connection == nil else { return }
        print("ANN - friends list :", self.idList)
        if let sess = Twitter.sharedInstance().sessionStore.session() {
            let swifter = Swifter(consumerKey: myKey, consumerSecret: mySecret, oauthToken: sess.authToken, oauthTokenSecret: sess.authTokenSecret)
            print("Starting stream")
            self.connection = swifter.postTweetFilters(follow: nil, track: tracker, locations: nil, delimited: false, stallWarnings: true, filterLevel: nil, language: nil, progress: { (json) in
                print(json)
            }, stallWarningHandler: { code, message, percentFull in
                print("ANN: Stall error ", message!)
            }, failure: { error in
                let err = error as! SwifterError
                print("ANN: Error ", err.message)
            })
        }
    }

Just wanted to throw this out there early to get some thoughts from the maintainers of the project (or anyone else, for that matter!).

Basically, I'm not a fan of using the JSON enum for consuming the Twitter API. It's much better than having to cast from Any all over the place, but it's still pretty inelegant--especially compared to what you can get away with in weakly-typed languages like JavaScript.

So, in parallel with a personal project of mine, I've been writing a wrapper API for Swifter, built on top of the Swift 4 Decodable protocol (actually originally built in private on top of the JSON type, then switched to Decodable). I intend to continue working on it no matter what, but I'm willing to go the extra mile and add support for all possible interactions with the API if it's decided that that would be within scope for the project.

The main alternative I can think of to building this wrapper (other than doing nothing) is the following:

• Provide generic methods for all API endpoints, which take generic success handlers, which take in arguments of type T where T: Decodable
• Defer creation of wrapper types to the user

Lastly, as of right now, all timeline and tweet methods have been implemented, and both demo apps have been updated to use the wrapper instead of the JSON API. Please feel free to ask questions, and give any feedback you have time to.

Thanks!

As mentioned in #203, I found my previous solution to this problem #196 had a few issues in practice. I also would prefer not to have to maintain an independent fork if I don't have to. So I decided to take another go at it, and the solution I came up with this time is more flexible, much simpler and more ergonomic than the old one. It's also slightly different from what I proposed in the above issue.

At the core of this pull request is a new type, RawSuccessHandler, which wraps a simple closure. A single parameter of this type is added to each endpoint method. The user can initialize it with one of three static methods to get either just the raw data, the raw data and a decoded value, or just a decoded value respectively--alternative name suggestions welcome:

• public static func data(handler: @escaping (Data) -> Void) -> RawSuccessHandler
• public static func dataAndDecoding<Entity: Decodable>(_ type: Entity.Type, handler: @escaping (Data, Entity?) -> Void) -> RawSuccessHandler
• public static func decoding<Entity: Decodable>(_ type: Entity.Type, handler: @escaping (Entity) -> Void) -> RawSuccessHandler

Behind the scenes, the closure wrapped by RawSuccessHandler itself accepts a Swifter.FailureHandler, which jsonRequest() takes advantage of to propagate decoding errors to the user-provided failure handler.

Below are some code samples.

Prints the home timeline in JSON form:

swifter.getHomeTimeline(
    rawSuccess: .data { data in
        print(String(data: data, encoding: .utf8)!)
    }
)

Prints the home timeline in JSON form, prints a belittling message, then prints a decoding error:

swifter.getHomeTimeline(
    rawSuccess: .dataAndDecoding(Int.self) { data, timeline in
        print(String(data: data, encoding: .utf8)!)
        print(timeline ?? "The home timeline isn't an integer, dummy!")
    },
    failure: { error in print(error) }
)

Prints the text of each tweet in the home timeline:

struct Tweet: Decodable {
    let text: String
}
swifter.getHomeTimeline(
    rawSuccess: .decoding([Tweet].self) { tweets in
        for tweet in tweets {
            print(tweet.text)
        }
    }
)

@mattdonnelly has been obviously busy in the past few months.

This made the repo development suffer quite a bit.

I honestly believe Swifter is an amazing framework and it would be a pity to see it die because of the lack of engagement of the repo owner.

I'd like to propose a solution: much like https://github.com/danielgindi/ios-charts , I propose that @mattdonnelly elects some Swifter collaborators, which are contributors enabled to manage the repo almost like if it was theirs (closing issues, merging pull requests and the likes) in order to have a better/faster Swifter development.

I'd say @meteochu is the most suitable for this position, but I leave to @mattdonnelly the final decision on the matter.

Please, feel free to share any thoughts on the issue.

let swifter = Swifter(consumerKey: TWITTER_CONSUMER_KEY, consumerSecret: TWITTER_CONSUMER_SECRET,appOnly: true)

this does not worked for me.

I Wants to login user from Twitter app as well as Authentication from browser.

From browser it's working.

But it is not redirecting to Twitter app.

I followed your tutorial and added swifter xcode project to my project, but I am getting 151 compilation errors saying - swift compilation error in the SwifteriOS xcode project.

I also tried to build swifteriOS project as it is and get the same compile errors.

I'm sorry if this is a stupid question, but I'm just learned about OAuth.

I'm using your library for my school's project.

how do I save the login session? so I don't need to relogin everytime I opened my application?

thank you very much and sorry for my bad English.

Hi,

I want to store tweets (JSON) as an array of NSString or NSData (and not array of JSONValue). I got raw NSString for a tweet using the 'description' property. Now I'm having trouble converting it back to JSONValue format so it's parameters can be accessed.

Is there a way to get raw JSON data and then convert it back to the Swifter's JSONValue format? Would be a big help.

Twitter's status id is now more than 2^32, so we cannot deal with the status id as Int with 32bit environment (such as iPhone4S).

For example, the code doesn't work correctly with iPhone4S, due to integer overflow.

let a:Int = 515496848048390145
print(a) //prints -289275903 

Therefore, I can't use func getStatusesShowWithID(id: Int, ...) to show https://twitter.com/gecko655/status/515496848048390145.

I think Swifter should include the same method with String argument, like func getStatusesShowWithID(id: String, ...), or should change the method to func getStatusesShowWithID(id: Int64, ...).

Is it correct?

Hello. The warnings are:

SwifterHTTPRequest.swift:170:31: 'init(request:delegate:)' was deprecated in iOS 9.0: Use NSURLSession (see NSURLSession.h)

and

String+Swifter.swift:57:22: 'CFURLCreateStringByAddingPercentEscapes' was deprecated in iOS 9.0: Use [NSString stringByAddingPercentEncodingWithAllowedCharacters:] instead, which always uses the recommended UTF-8 encoding, and which encodes for a specific URL component or subcomponent (since each URL component or subcomponent has different rules for what characters are valid).

I realise these are tiny problems, but I haven't done any programming since May 2015, and I feel that I might cause more harm than good by trying to fix them myself just yet, so just flagging them up for others until my mind is more Swift 2.0 attuned. JBM.

Everytime I try to run this code, it breaks:

    var swifter = Swifter(consumerKey: "MY_API_KEY", consumerSecret: "MY_SECRET_KEY")
    swifter.getListsStatuesWithSlug("xxxxxx", ownerScreenName: "xxxxxx", sinceID: nil, maxID: nil, count: nil, includeEntities: false, includeRTs: false, success: {

        (lists: [JSONValue]?) in


        }, failure: {

            (error: NSError) in

            NSLog(" error => %@ ", error.userInfo)

    })

It seems to do this with a few other swifter functions I have tried, none of them have worked so far.

It breaks in the SHA1DigestWithKey func in the Swifter+String.swift class: CCHmac(CCHmacAlgorithm(kCCHmacAlgSHA1), keyStr!, keyLen, str!, strLen, result)

EXC_BAD_ACCESS(Code = 1, address = 0x14)

TL;DR This package will be deprecated in about one month. I'm not going to delete it for now but will no longer be maintaining it officially.

Hi everyone,

I created this project back when Swift was a very new language, as a way of learning it and sharing ideas on how to deal with APIs using it. Since then, it's grown a lot of in popularity and has been used by more people than I had ever imagined, which was been amazing to see.

Unfortunately, I haven't had time to contribute actively to this project for several years. For a long time, I relied on other people who did a far better job at maintaining it than me. However, over time this repo has slipped out of date with Twitter's API and there's been less and less activity here.

As a result, I've decided to officially deprecate this project in about one month from now. This means there will be no future changes to the repo, so on the off chance that anyone is still using this, you should seek out alternatives now. To deprecate it I will be will be taking the following steps:

• Remove all collaborators with write access to prevent future changes
• Update the README to indicate the project is no longer maintained and link here
• Edit the README and repo description to indicate the project is no longer maintained
• Add a deprecated GitHub topic

My goal here is to prevent this from becoming yet another horror story about an inactive developer of a widely used library unintentionally distributing malware.

I don't plan to the delete or transfer the repo to prevent it suddenly breaking people's code, but if anyone has other recommended courses of action or questions please leave them here.

Massive thanks to everyone that has contributed and helped maintain this project thus far. Especially @meteochu and @zntfdr. I'll follow up here in a months time once I begin taking the steps to deprecate the project.

if I understand correctly

• Swifter initializer that takes the following consumerKey, consumerSecret, oauthToken, oauthToken secret is actually means request is sent through user's quota?
• Swifter initializer that takes the following consumerKey, consumerSecret is actually means request is sent through developers quota?

  self.swifter = Swifter(consumerKey: Constants.TWITTER_CLIENT_KEY, consumerSecret: 
  self.swifter.authorize(withCallback: URL(string: "myApp://")!, presentingFrom: self, success: { accessToken, _ in
            print(accessToken)
        }, failure: { _ in
            print("ERROR: Trying to authorize")
        })

I also added callback_url is "myApp://" on developer.twitter.com. But It's throw error: CredStore - performQuery - ``` Error copying matching creds. Error=-25300, query={ class = inet; "m_Limit" = "m_LimitAll"; ptcl = htps; "r_Attributes" = 1; sdmn = "https://api.twitter.com"; srvr = "api.twitter.com"; sync = syna; }

not sure if this repo is still active but the sample usage is not recommendable anymore since it's deprecated on ios13 so currently im trying to run ios15 so now I can't use the deprecated one.. I'm using the one who has a parameter of ASWebAuthenticationPresentationContextProviding but im still in progress and not sure if it'll work as expected.