Xcode Compile Flag to Suppress Nullability Warnings not Working?

Question

For a limited time I want to suppress these kind of warnings the compiler is showing me in Xcode 7.3.1:

<File>: Pointer is missing a nullability type specifier (_Nonnull, _Nullable, or _Null_unspecified)

I have added this compiler flag to all classes under My Target/Build Phases/Compile Sources: -Wnullability-completeness

But it's not working - the warnings are still shown. How can I get rid of the warnings?

Did you clear out the existing warnings? – NRitH Jun 07 '16 at 23:33 — NRitH, Jun 07 '16 at 23:33

score 42 · Accepted Answer · answered Jun 07 '16 at 23:35

42

To disable those warnings, you want: -Wno-nullability-completeness. Note the no-; the flag you're using enables those warnings.

answered Jun 07 '16 at 23:35

Carl Norum

219,201
40
422
469

5

Cool, that worked on the .m files. Any idea how to disable it for the .h files? – electronix384128 Jun 07 '16 at 23:57
7

I added this in XCode 9 (or 8) by adding it to `Build Settings` -> `Apple LLVM 9.0 - Custom compiler flags` -> `Other Warning Flags`. You can just search for `Other Warning Flags` – xaphod Sep 15 '17 at 20:08
4

In Xcode 10, this was moved to Apple Clang - Custom Compiler Flags > Other Warning Flags – Dávid Pásztor Apr 17 '19 at 13:26

RunLoop · Answer 2 · 2019-11-07T12:22:26.867

9

Note that in Xcode 11 it is now -Wno-nonnull

It should be set in "Other Warning Flags" in the "Apple Clang - Custom Compiler Flags" section of your target.

You could also avoid these warnings and setting the above altogether by removing these flags Xcode automatically adds to new header files in Objective-C:

NS_ASSUME_NONNULL_BEGIN
NS_ASSUME_NONNULL_END

edited Nov 07 '19 at 12:22

answered Sep 26 '19 at 05:10

RunLoop

20,288
21
96
151

1

Sorry under which field to set this flag in Xcode 11? – hyouuu Nov 06 '19 at 21:45
1

@hyouuu I have updated the question to show where it should be set. – RunLoop Nov 07 '19 at 03:13

score 8 · Answer 3 · answered May 29 '20 at 12:10

8

Settings for Xcode 11.5 when using project with mixed sources, ObjC and Swift:

WARNING_CFLAGS = $(inherited) -Wno-nullability-completeness
OTHER_SWIFT_FLAGS = $(inherited) -Xcc -Wno-nullability-completeness

answered May 29 '20 at 12:10

Vlad

6,402
1
60
74

score 5 · Answer 4 · answered Feb 06 '20 at 08:59

In Xcode 11.3, these started appearing out of nowhere in my pure Swift project on the Github ci. That was because I am importing the AWS Objective-C SDK.

Confoundingly, this would only occur on the first build, probably creating the module map for the framework. Hence it was only a problem on ci because of the clean builds.

Fixed it by adding this to the Swift compiler options (search for OTHER_SWIFT_FLAGS in your build settings):

-Xcc -Wno-nullability-completeness

Xcode Compile Flag to Suppress Nullability Warnings not Working?

4 Answers4

Linked

Related