Silencing the error caused by implicitly using a nullable pointer in a non-null context. Simply storing the value into a variable first silences the warning but this does not fix the underlying, potential, problem. The numbers can still be null, which will cause an exception when accessed in an array.

Code signing was disabled as this is not required for at the framework level. Frameworks are embedded into applications so only the final app needs to be signed.

Enabled new warnings to help catch some common and obscure errors such as infinite recursion, autorelease objects being captured by blocks, etc.