Hello...
There doesn’t seem to be anything wrong with your line of code, but there could be a problem somewhere else (or with how/where you’re writing the code for the completion handler block).
I’ve run into problems a few times where the compiler didn’t report errors properly or gave cryptic error messages, but I was usually able to figure out my mistake by breaking out the offending line into individual statements so that I got a better error message from the compiler (except for one time, where a mistake in declaring a function compiled cleanly and then later on segfaulted the compiler when it was called; 19437380).
To isolate the problem, I’d try declaring the completion handler function separately and then pass in the function.
func testHandler(myData: NSData!, myResponse: NSURLResponse!, myError: NSError!) -> Void // try your handler code here let task = session.dataTaskWithRequest(request, completionHandler: testHandler)
If Xcode accepts your handler code that way and accepts the function as a parameter, you might have a mistake in how you’re adding your handler code to the inline closure in the line you posted. If you post the code showing how you are adding the handler code to the original line you posted, we could rule that out.
Louis
| Well it was a nice though, but the session variable is created with:
let session = NSURLSession(configuration: config)
And it’s not an optional (just a NSURLSession type) , so that theory is out :( On Mar 5, 2015, at 2:28 PM, John Tsombakos < email@hidden> wrote:
I will have to check it when I get home, that sounds plausible. However it build and runs just fine. But with all the Swift-y oddness, I'm not surprised by anything. (Of course, the SourceKit service shouldn't crash either, so...)
Thanks.
|
|