Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    tuntruong
    @tuntruong
    plz
    girishghoda
    @girishghoda
    Anybody help how to fix?
    plz
    Thank you
    girishghoda
    @girishghoda
    Screen Shot 2018-02-24 at 3.22.35 PM.png
    Rahul Katariya
    @RahulKatariya
    @girishghoda Restart your mac once
    girishghoda
    @girishghoda
    @RahulKatariya thank you its work normally, headache around 2 hour :smile:
    Sean Molenaar
    @SMillerDev
    Hey guys, I posted a question about favicon support in AlamofireImage a while ago (Alamofire/AlamofireImage#307) but there's no response yet
    What's the best place to ask those kinds of questions?
    Jon Shier
    @jshier
    @SMillerDev Sorry, haven’t looked at AFI in a bit. I’ll take a look tonight. For your issue, generally, as long as Apple’s OSes can render those images without extra software on all platforms, then a PR would be great.
    Sean Molenaar
    @SMillerDev
    @jshier Yeah should be the exact same image just by a different name/mimetype
    Jon Shier
    @jshier
    Looking into it more, it may be okay, though we’ve resisted adding non-standard MIME types before.
    It’s easy to add your own at runtime though.
    We’ll discuss it.
    Sean Molenaar
    @SMillerDev
    But it is the official standard :smile:
    Santiago Apaza
    @focker321
    Hi, someone knows how to load instead of a rest service a local file (json)???
    Jon Shier
    @jshier
    @focker321 If you mean for mocking, you can try a library like OHHTTPStubs.
    steffen25
    @steffen25

    Hi, Im trying to send a GET request with Alamofire but for some reason my query param gets urlencoded e.g.

    http://localhost:8080/v1/posts/?name=name-here will turn into
    http://localhost:8080/v1/posts/%3Fname=name-here

    I would appreciate if someone could tell me how to stop urlencoding my request with Alamofire

    steffen25
    @steffen25
    I got it working, I had to use the URLEncoding
    Tritium7
    @Tritium7
    Hi, could anyone help me with Xcode + Alamofire issue? : https://stackoverflow.com/questions/50320089/xcode-no-such-module-alamofire
    Jon Shier
    @jshier
    We have manual integration directions in our README. Make sure you follow those directions closely and it should work fine. If you find something specifically wrong with the directions, feel free to file an issue an let us know. Otherwise this isn’t something we can help with very well, given the number of factors involved and Xcode’s well know issues in the area.
    Tritium7
    @Tritium7
    I installed with Git based on your Readme. And the strange thing that its working okay for build, after 4-5 tries. But for archive the Xcode complains.
    I guess I will try with a dependency manager. Any suggestions?
    Jon Shier
    @jshier
    For manual integration, make sure it’s being included in all of your build configurations. For a dependency manager I like CocoaPods, just make sure you have a managed Ruby environment underneath (RVM or rbenv). Carthage works but it still requires manual integration.
    Tritium7
    @Tritium7
    CocoaPods solved the problem! Thanks!
    Jesús
    @jesmg
    Hi. I have a problem with Alamofire and i'm looking for some help :)
    I have a server with the certificate "A". A is child of (signed by) B, and B is child of (signed by) C.
    If I do certificate pinning with C, everything is ok
    Now I have a new version of "B", which has a cross-reference sign with "D"
    So B is a valid certificate for C and D chain of trust
    But If I do pinning with D... Alamofire says the pinning failed
    I'm afraid Alamofire is ignoring the cross reference :/
    this is a bug or maybe i'm doing something wrong?
    Jon Shier
    @jshier
    @jesmg Are you sure the cross signing is correct? Alamofire support cross signing, as that’s what Lets Encrypt uses for its certs, which are used by many clients.
    donners
    @donnersyt
    Hi, I was wondering if it is possible to use HTTP and HTTPS proxies for requests sent through Alamofire on iOS 11 as this demo code does not appear to work for me! https://stackoverflow.com/questions/42616908/how-to-use-a-proxy-server-with-alamofire-4-and-swift-3
    Jon Shier
    @jshier
    It should work, as Alamofire just uses the underlying URLSession functionality. If it’s not working for you, I’d suggest checking your proxy setup and investigating any errors you’re getting from the connection.
    donners
    @donnersyt
    @jshier HTTP requests work ok, but anything over HTTPS returns Error: Optional(Error Domain=kCFErrorDomainCFNetwork Code=310 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2096, _kCFStreamErrorDomainKey=4})
    HTTPS requests work fine when I use the same proxy through my System Settings on my Mac. Do you think I need to change my Info.plist file, as I had to do so in order to be able to send HTTP requests
    Jon Shier
    @jshier
    As long as your HTTPS proxy uses HTTPS for your connection to it, you shouldn’t need to change anything for ATS. Well, unless your proxy connection doesn’t support the encryptions or TLS versions required. Does it?
    Does the error you get have a description or localizedDescription?
    From quick Google it seems likely that error is due to a cert issue when using the proxy. Is it something you can control or fix? Otherwise you might need an ATS exception in your Info.plist.
    Jon Shier
    @jshier
    Also, if you’re manually setting any proxy headers (Proxy-Authenticate or Proxy-Authorization) on a per-URLRequest level, you may want to try moving those headers to the URLSessionConfiguration’s additionalHTTPHeaders property.
    Rick Consuelo Sanchez
    @ricksanchezisagoodman
    hey all! is this the place to ask questions how to use alamofire?
    Jon Shier
    @jshier
    @ricksanchezisagoodman Sure, though we aren’t around much, so Stack Overflow is another option.
    Vikas Singh
    @VikasSingh-NITB
    Hi All....I have applied swizzling on dataTask method from URLSession and its working properly...but its not working for Alamofire request method...any idea...??
    Vikas Singh
    @VikasSingh-NITB
    Anybody help me...??
    Alexis A. Banaag Jr.
    @aabanaag
    Hi, I'm doing a photo upload to our Google Cloud storage but when I try to do multipart upload it fails and returns an error . It shows an error that the bytes are in mismatch. that it expect XXX more than the one it contains. The problem is the size and the image have no changes before the call is being processed. But when I did Alamofire.upload(data, to: URL) it works instantly. Any insights onto why?
    Alexis A. Banaag Jr.
    @aabanaag
    Optional("Invalid request. There were 5583 byte(s) (or more) in the request body. There should have been 5404 byte(s) according to the Content-Range header.") this is the sample error I get when I try to implement a multipartForm upload.
    Jon Shier
    @jshier
    @VikasSingh-NITB Without knowing more about what you’re swizzling, why, and what’s not working, there’s not much we can help you with here. Alamofire doesn’t test any compatibility with swizzling URLSession internals.
    Jon Shier
    @jshier
    @aabanaag Looks like you’re trying to support Drive’s resumable uploads. Those don’t seem to be the same as their multipart uploads, so it doesn’t seem like you can or should combine the two. So you’ll probably need to choose one method and use that, or perhaps use their SDK.