Ok, finally after hours of trial and error I found the solution for this problem. You should never ever execute parse calls in the header of view controllers, as these calls could be executed before the API registration. For example: class ViewController: UIViewController { // this will crash the app...
ios,uitableview,swift,parse.com,pfimageview
Without using cache, the workaround I found is to first set the image file in cellForRowAtIndexPath to the placeholder image, and then if the image object was found on the server, the cells image is set to the new file, and then loads it in the background. Here is the...
swift,class,parse.com,pffile,pfimageview
Parse allows you to add columns to a class lazily, meaning that you can add a field to your PFObject and if it is not present in your Parse class, Parse will add that column for you. Here's how you would add a column via code: // Prepare image let...
Why don't use PFFile instead? For loading an image from data you can do like this: PFFile *fileImage = your_file; [fileImage getDataInBackgroundWithBlock:^(NSData *imageData, NSError *error) { UIImage *image = [UIImage imageWithData:imageData]; yourImageView.image = image; }]; And for the PFQuery replace that method with this block: [query findObjectsInBackgroundWithBlock:^(NSArray *objects, NSError *error)...
ios,objective-c,parse.com,pfimageview,pfcollectionviewcell
The problem you are facing is that you are registering the class in your -viewDidLoad method, but you are setting up your cell via the Prototype cell in Storyboard. If you refer to the "Cell and View Reuse" section here, you will read (emphasis mine): ... if the cell or...
ios,swift,parse.com,pfimageview
With content mode set to Aspect Fill, try setting clips to bounds to true as well, reason being the content mode aspect fill keeps on filling the frame of the image view till the frame is fully filled with content also keeping the aspect ratio intact. In the process of...