16

I upgraded to Xcode 6.3 yesterday. Since then, I have been unable to build anything that has Parse.framework in it. For PFConstants.h I get errors like

nullability specifier '_nullable' cannot be applied to non-pointer

I have never seen this error before, and changed nothing other than updating to 6.3. Any ideas?

user717452
  • 33
  • 14
  • 73
  • 149

2 Answers2

19

Parse has implemented the new nullability annotations that are available in Xcode 6.3 - See their blog post, but it seems the approach in their old framework causes these compilation errors.

Simply update the Parse frameworks from the latest API downloads and you will be back in business

Paulw11
  • 108,386
  • 14
  • 159
  • 186
  • 2
    That was it. Thanks for quick answer. Crazy that one update caused so many problems. – user717452 Apr 10 '15 at 04:01
  • 2
    I'm having this same issue, and I've removed the old version of Parse and replaced it with the new one and this error (along with others is still appearing). Is there anything I should be doing besides removing the frameworks and adding the updated version? At the moment I'm also getting a 'Failed to import briging header' error as well as 'Could not build module ParseUI' in addition to the nullability errors – SamYoungNY Apr 13 '15 at 01:49
  • Same error here, can't build the project... @SamYoungNY you find a clue ? – Clément S. Apr 13 '15 at 16:58
  • Not yet... @BergzBoy you can check this link out which I didn't find too useful but you might https://groups.google.com/forum/#!topic/parse-developers/im-bNTazInU --- I started a ticket here too: https://groups.google.com/forum/#!topic/parse-developers/p-k-hJGuofA – SamYoungNY Apr 13 '15 at 17:18
1

This seems to be an issue with the version of Parse you are using. Although an obvious answer is to update your versions of Parse this can cause knock on effects in the app.

I didn't want to update to the latest version of Parse as this would require significant changes to adapt to the new Facebook SDK and other needed libraries.

I found that this fix worked well for getting the project compiling and working:

Switch around the location of PF_NULLABLE_S in the problem variables and it seemed to fix the issue

So switch this:

typedef void (^PFArrayResultBlock)(PF_NULLABLE_S NSArray *objects, PF_NULLABLE_S NSError *error);

to this:

typedef void (^PFArrayResultBlock)(NSArray * PF_NULLABLE_S objects, NSError * PF_NULLABLE_S error);

This enabled my apps to compile and run as normal without changing the libraries. This answer is certainly not a fix to the underlying issue but is very useful in many situations eg. you want to be able test an older version, don't want to update it yet but still want to be able to run it

sam_smith
  • 6,023
  • 3
  • 43
  • 60