Would ignoring the yellow warnings that show up when I run profiler be an a issue if no warnings show up when I build and run my project in XCode?

Question

Coming to the end of a project and it has been a long few months of a mixture of stress and relief. I'm testing the app using instruments now and noticed when I run profile I get a bunch of yellow warnings that never showed up when I built and run a project are showing up.

They all seem to be integer based and XCode will automatically correct them for me if I choose to do so.

Here are some of the errors:

I'm wondering whether these warnings would cause performance issues if ignored?

I'm a little hesitant to correct them because I have a feeling they will cause issues in parts of my app (which shouldn't be an issue because the main aim is to get an error free app in the app store). But you know when you've spent countless weeks on a large project and become sick of working on it... yea.

I can go ahead and correct them but is XCode ever wrong when it comes to correcting these integer type warnings?

A lot of the warnings seem to be on lines similar to these:

I'd be interested in reading your views.

Thanks for your time.

Answer 1

Are you compiling 32 bit for the simulator vs. 64 bit when running instruments (you may be compiling to run on an actual iPad air or something)? I'd urge you to clean up these warnings in order to be 64 bit compliant.. NSInteger is int64 (long int) on 64 bit platforms and int 32 on 32 bit platforms. Its complaining because the type in the string doesn't match the type given when its compiled as a 64bit binary.

There are several ways to fix this. One method is to convert the number into an NSNumber using the @() syntax and then use %@ in your format strings (thanks Sulthan). You could also either explicitly upcast to a long int and then use %li in the format string, or explicitly downcast to an int (these options are more performant because you don't have to instantiate an NSNumber every time).