fatal error: unexpectedly found nil while unwrapping an Optional value about alamofire HOT 8 CLOSED

Same here. Looks like data is nil there for some reason. error is also nil fwiw. Not sure why yet.

from alamofire.

I see this error even using the example from http://nshipster.com/alamofire/.

Alamofire.request(.GET, "http://httpbin.org/get")
         .responseJSON {(request, response, JSON, error) in
             println(JSON)
         }

from alamofire.

        return { (request, response, data, error) in
            var serializationError: NSError? // never assigned or unwrapped
            let JSON: AnyObject! = NSJSONSerialization.JSONObjectWithData(data, options: options, error: &serializationError)
            return (JSON, serializationError)
        }

As I wrote in the code above, var serializationError is never assigned to the error passed in the closure. I'll submit a pull request soon to fix this.

from alamofire.

Simply adding = error fixes the issue, but I'm not sure if it's up to the consumer to unwrap the error?

from alamofire.

If it's named serializationError I don't think setting it to error is correct. I think JSONObjectWithData is meant to put something in there.

from alamofire.

I have similar situation only for iOS 7 targets, got nil for data, but iOS 8 targets runs fine.

from alamofire.

Ah, I'm using an iOS 7 phone. Looks like it works with an iOS 8 simulator. Wonder what the difference is.

from alamofire.

Fixed by #34.

from alamofire.