If you're also doing your Unity game on those platforms, make a build there, have it generate the Xcode project, and use Xcode to turn on the iCloud capability and set up CloudKit. Again, you can do all the primary work on the iOS/tvOS App ID. But the secondary one will need to have a different name.īoth App IDs will need to have the iCloud/CloudKit capability set. With iOS/tvOS being the flagship platforms, it probably makes more sense to create your primary App ID for them and have a secondary one for macOS. You can only create App IDs that target either iOS/tvOS or macOS. Our goal is to have iCloud support (through CloudKit) across all platforms: iOS, tvOS, and macOS. You can either create one yourself on or have Xcode do it for you.
#Upgrade unity cloud build fail mac#
You do specifically need a Mac Development certificate. We are working on a development version for the moment, so you only need a development certificate. Things with Apple keep changing, so the blog post you're reading now is accurate for the summer of 2019, but may become less so as Apple changes things in the future.Īlso thank you to eppz! Appcrafting for their amazing work digging into the bits and pieces of Unity so they could point us at the tools we needed to finally solve CloudKit access.
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).
0 kommentar(er)
