Warning: “format not a string literal and no format arguments”

Since upgrading to the latest Xcode 3.2.1 and Snow Leopard, I’ve been getting the warning

“format not a string literal and no format arguments”

  • Get xcode 4.5 to warn about new API calls
  • alternative to deprecated UITableViewCell setText?
  • Ignore Xcode warnings when using Cocoapods
  • How does one change the color for text highlighting in Xcode 4 for warnings and errors?
  • suppress instance method override linker warning framework xcode
  • Xcode stupid warning: View is clipping its content
  • from the following code:

    NSError *error = nil;
    if (![self.managedObjectContext save:&error]) 
        NSLog([NSString stringWithFormat:@"%@ %@, %@", 
           [error userInfo]]);      

    If errorMsgFormat is an NSString with format specifiers (eg: "print me like this: %@"), what is wrong with the above NSLog call? And what is the recommended way to fix it so that the warning isn’t generated?

    11 Solutions Collect From Internet About “Warning: “format not a string literal and no format arguments””

    Are you nesting your brackets correctly? I don’t think NSLog() likes taking only one argument, which is what you’re passing it. Also, it already does the formatting for you. Why not just do this?

    NSLog(@"%@ %@, %@", 
       [error userInfo]);              

    Or, since you say errorMsgFormat is a format string with a single placeholder, are you trying to do this?

    NSLog(@"%@, %@", [NSString stringWithFormat:errorMsgFormat, error], 
       [error userInfo]);              

    Xcode is complaining because this is a security problem.

    Here’s code similar to yours:

    NSString *nameFormat = @"%@ %@";
    NSString *firstName = @"Jon";
    NSString *lastName = @"Hess %@";
    NSString *name = [NSString stringWithFormat:nameFormat, firstName, lastName];

    That last NSLog statement is going to be executing the equivalent of this:

    NSLog(@"Jon Hess %@");

    That’s going to cause NSLog to look for one more string argument, but there isn’t one. Because of the way the C language works, it’s going to pick up some random garbage pointer from the stack and try to treat it like an NSString. This will most likely crash your program. Now your strings probably don’t have %@’s in them, but some day they might. You should always use a format string with data you explicitly control as the first argument to functions that take format strings (printf, scanf, NSLog, -[NSString stringWithFormat:], …).

    As Otto points out, you should probably just do something like:

    NSLog(errorMsgFormat, error, [error userInfo]);

    Final answer: As Jon Hess said, it’s a security issue because you’re passing a WHATEVER string to a function expecting a format string. That is, it’ll evaluate all format specifiers WITHIN the whatever string. If there aren’t any, awesome, but if there are, bad things could happen.

    The proper thing to do, then, is USE a format string directly, for example

    NSLog(@"%@", myNSString);

    That way, even if there are format specifiers in myNSString, they don’t get evaluated by NSLog.

    I don’t especially recommend using this, since the warning IS a real warning.. in a dynamic use of the language it’s possible to do things runtime to the string (i.e. insert new information or even crash the program).. However it’s possible to force suppress if you KNOW that it should be like this and you really don’t want to be warned about it..

    #pragma GCC diagnostic ignored "-Wformat-security"

    Would tell GCC to temporarily ignore the compilation warning.. Again it’s not solving anything but there may be times when you can’t find a good way to actually fix the problem.

    EDIT: As of clang, the pragma has changed. See this: https://stackoverflow.com/a/17322337/3937

    Quickest way to fix it would be to add @"%@", as the first argument to your NSLog call, i.e.,

    NSLog(@"%@", [NSString stringWithFormat: ....]);

    Though, you should probably consider Sixteen Otto’s answer.

    I’ve just been passing a nil to negate the warnings, maybe that would work for you?

    NSLog(myString, nil);

    NSLog() expects a format string, what is getting passed in is just a string. You do not need to use stringWithFormat:, you can just do:

    NSLog(@"%@ %@, %@", errorMsgFormat, error, [error userInfo])

    And that would make the warning go away.

    If you want get rid of the warning “format not a string literal and no format arguments” once and for all, you can disable the GCC warning setting “Typecheck Calls to printf/scanf” (GCC_WARN_TYPECHECK_CALLS_TO_PRINTF = NO) in your target’s build settings.

    FWIW, this applies to iPhone dev as well. I’m coding against the 3.1.3 SDK, and got the same error with the same problem (nesting stringWithFormat inside NSLog()). Sixten and Jon are on the money.

    Just letting anyone know using the appendFormat on NSMutableString can also cause this warning to appear if trying to pass in a formatted string like so:

    NSMutableString *csv = [NSMutableString stringWithString:@""];
    NSString *csvAddition = [NSString stringWithFormat:@"%@",WHATEVERYOUAREPUTTINGINYOURSTRING];
    [csv appendFormat:csvAddition];

    So to avoid this warning, turn the above into this:

    NSMutableString *csv = [NSMutableString stringWithString:@""];

    More concise and more secure. Enjoy!

    NSLog(@"%@ %@, %@", 
           [error userInfo]);