PFThreadsafetySafeDispatchSync Crash on PFThreadsafety.m:28

[maxbryan]

Getting a crash while trying to get an image file's data. Calling getDataInBackgroundWithBlock on the main thread. The crashing code is called from PFFile downloadAsyncWithProgressBlock.

    image.getDataInBackgroundWithBlock {
        (data, error) -> Void in

        if let data = data {

            if let image = UIImage(data: data) {

                self.imageView.image = image
            }
        }
    }

crash source: 0 dispatch_queue_get_specific

[maxbryan]

Looks like this happened when trying to get data from a nil PFFile

[parse-github-bot]

Thank you for your feedback. We prioritize issues that have clear and concise repro steps. Please see our Bug Reporting Guidelines about what information should be added to this issue.

Please try the latest SDK. Our release notes have details about what issues were fixed in each release.

In addition, you might find the following resources helpful:

• Documentation: https://www.parse.com/docs
• Google Groups: https://groups.google.com/forum/#!forum/parse-developers
• Stack Overflow: http://stackoverflow.com/tags/parse.com

[richardjrossiii]

This should never happen when a PFFile is nil, as messages sent to nil should always be a no-op. Can we get a full stack trace? (type thread backtrace all in the LLDB console).

[maxbryan]

Here's a full trace. Thanks again for your help

[richardjrossiii]

Thanks for the stack trace... What version of the SDK are you using? That stack trace indicates that the crash is on line 298 of PFFile, though in the latest version of the SDK line 298 is doing something completely different.

[maxbryan]

Looks like 1.7.5

[richardjrossiii]

Parse 1.7.5 was released in almost 3 months ago, and is no longer supported. Please try using the latest version of Parse, which is 1.8.4. If the problem still persists, post a stack trace with the current version of the SDK so that we can help you better.

[maxbryan]

Problem still exists with the newest SDK.

[richardjrossiii]

Are you ever creating a PFFile via a method other than -[PFFile fileWith...]? What appears to be happening is that the file's internal dispatch queue is NULL, which should only ever happen if the file was not created through one of our dedicated constructors.

[maxbryan]

I'm initializing a variable with PFFile() at the header of my swift document then getting the file from the server then assigning it to that variable. I recently changed it so that if the image doesn't exist on the server, I assign nil to it and it seems to be working correctly now.

[nlutsenko]

Yup, sounds like we didn't mark that method as unavailable...
Going to fix in a bit.