- Home /
Best Practices: Compiling for iOS
Still working on my first project, I'm close to MVP being ready for submission. Everything works/runs as intended across all devices. However, when building/archiving my product in Xcode, I get upwards of 50-60 warnings - not errors, but warnings - and I'm curious if the expectation should be that I clear out these warnings before submitting my Unity-based app to Apple's app store.
From deprecated functions to - well, actually it's mostly deprecated functions. Should I manually go in and update those? (Mind you, there'll be a learning curve to learn enough about iOS development separate from Unity, but I'm willing to put in the work.)
Thoughts? Feelings? Ice Cream Flavours?
Cheers!
Your answer
Follow this Question
Related Questions
Unity 3.5 Xcode crash, compiler error iOS 5.01 0 Answers
How to compile code only for both Android and iOS? 1 Answer
iOs Apps overwriting each other 1 Answer
iOS plugin using .a is ignored when compiling Xcode project generated by Unity? 1 Answer
What C# packages should be avoided to avoid JIT compile errors on iOS 0 Answers