Introduction - Learn SpriteBuilder for iOS Game Development - page 12

Once you have an example project opened in SpriteBuilder, you have to publish it. The
published resource files have been stripped from the Xcode project to reduce the archive
size.
When you open the SpriteBuilder project's Xcode project and build it, you may get warn-
ings or even errors. The projects were all tested with Xcode 6.0. If you're using Xcode 6.1
or later, there's a chance that Apple made changes and improvements to the build settings
and compiler. For instance, you may be asked to update the project's Build Settings or
format. This is usually safe to do.
Note The first time you run the Xcode project, it may appear to hang or take a
very long time to complete. This may happen in particular when you haven't
previously opened the SpriteBuilder project and published it. In that case,
Xcode will launch the publish process for the SpriteBuilder project, but it won't
give you any progress indication. Therefore, it's recommended that you open
and publish the SpriteBuilder project first—that way, at least you get a progress
indicator.
You may get some compiler warnings or errors pointing out potential problems in the
code. If there are warnings originating from one of the library targets (Cocos2D, Ob-
jectAL, or Chipmunk), you can ignore those. They are typically uncritical and may even
persist for several releases. The Cocos2D developers clean up warnings from time to time.
New errors in previously perfectly acceptable code can occur, too. Usually this happens
with newer Xcode versions, where the compiler now treats certain cases of warnings as
errors, or it simply finds new potential issues in general. As long as they're only warnings,
ignore them. They are most likely artifacts caused by advancements in Xcode.
However, if you get compiler errors in the libraries, you may want to try updating Co-
cos2D to see if the warnings/errors go away. If there's an error in the project's code itself
(the code in the Source group) and you can't fix it by yourself, please check the
SpriteBuilder forum at http://forum.spritebuilder.com for errata and fixes.
Of the 17 SpriteBuilder projects, the majority were originally created with SpriteBuilder
versions prior to v1.3. Therefore, the projects numbered 00 to 13 do not contain the neces-
sary code to compile them for the Android platform. The projects numbered 14 through
16 do have Android support. Accordingly, the projects 00 to 13 will have different items
in the schemes and platform lists than projects 14 through 16.