Hi,
I've heard that if you want to publish your app to the App Store, it's okay to have warnings from Xcode as long as they're not critical to the apps stablitity or performance. Of course, getting rid of them is the best option, but in this case, there are over 999+ warnings generated by a third-party app.
In my case is that I'm working on an app in Unity, and I'm getting a lot of Unity-generated warnings that I assume are benign, but I don't want to risk delaying the app's review process.
I receive the following warnings:
-This function declaration is not a prototype
-Code will never be executed
-All paths trough this function will call itself
-Unused function
-OSAtomicCompareAndSwap32Barrier is deprecated
Is there an app that has been allowed entry to the AppStore with these warnings? It it okey for me to publish the app on AppStore with these warnings or how should I approach this issue?
Thank you
Mike
Your source code is not uploaded to the App Store, so Apple will not be looking at those warnings.
There are different views on it:
- Some people treat warnings the same as errors - they must be fixed.
- Other people take a more relaxed view - some warnings are trivial, and cause no harm.
My personal approach is to allow some warnings during development (e.g. when using TestFlight), but I like to clear them all before submitting to the App Store.