This guide is thorough and well-referenced. (Edit: Link to part 2)įirst off, a huge debt of gratitude to the folks who put together the Unity Apple Distribution Workflow document. Part 2 will (eventually) detail changes you need to make to make the game viable to upload to the App Store and distribute generally. set up, as well as the process of getting your game built and signed correctly to run in a development environment. Part 1 of this process will detail getting signing identities, App IDs, provisioning profiles, etc.

(There do seem to be plans to change this.) Our task is doubly complicated because the game needs to be released not only on the Mac App Store, but also as a standalone product and still have access to CloudKit features. Unity still uses a precompiled binary executable (even with IL2CPP builds) and does not generate an Xcode project that will handle all of your codesigning and entitlement needs. There's a lot of good documentation out there for iOS and tvOS, and Unity provides good tools for exporting the projects to Xcode and letting you build things in Apple's environment with all of their tools readily available. We are in the process of developing several games for various Apple products, and we're using CloudKit to keep game saves in sync across the various platforms (iOS, tvOS, macOS).

Ios cridentials for unity cloud build