|
wwb posted:Some of this probably has to do with limited seat time building stuff on macs but then again I got android building release / store ready signed artifacts inside of an hour so it can't be that tricky. I'm the "automated Android and iOS builds" developer where I work. The actual process of building release artifacts can be very simple for both platforms. Getting to this point in iOS is much more difficult than it is with Android because of code signing. Here's what I did: Setup:
The import step puts everything in a login keychain. Current build script:
The previous build script specified identity and the .mobileprovision filename. However, release build uploads started failing when we switched from a Mac Mini (setup by a consultant with his account) to a virtual Mac (setup by me). Builds were successful but were signed with the wrong certificate. The only way I knew to fix it was by using Xcode defaults for the identity and provisioning profile. Shenzhen can easily do that, so I used that instead of writing my own build script. Thankfully, the build server is now capable of building all 60+ apps. The previous script used an incorrect provisioning profile for a few apps (despite matching bundle IDs).
|
#
¿
Jan 31, 2015 17:43
|
|
|
|
| # ¿ Apr 29, 2024 05:14 |
|