You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: jekyll/_docs/ios-builds-on-os-x.md
+41Lines changed: 41 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,47 @@ versions installed:
28
28
- carthage 0.16.2
29
29
- shenzhen 0.14.2
30
30
31
+
## Simulator UUIDs
32
+
33
+
When targeting a specific iOS simulator with the `-destination` flag, we suggest that you use one of these UUIDs instead of a combination of `-destination 'platform= , name='`.
description: Common problems with iOS and OSX builds
7
+
---
8
+
9
+
10
+
11
+
There are common problems you might run into during the initial setup of your CI/CD setup with CircleCI or even issues that only occur when your project has grown to a certain size.
12
+
13
+
14
+
## Xcode Toolchain errors
15
+
16
+
### xcodebuild exit code 65
17
+
There are plenty of reasons why exit code 65 could be thrown, as it is a general error returned for bad user input. Sometimes that is not the case though, since all your builds run in a container your builds also have to share system resources with other builds. Exit code 65 is mostly the issue of a lack of enough CPU power to launch the iOS simulator in time for the test to run once xcodebuild'S `test` action is called, and the tests simply time out.
18
+
A way to mitigate this is to launch the iOS simulator as a part of your dependencies block in your CircleCI configuration file.
This will launch the simulator just like it would if you'd hit `CMD + R` on your machine in Xcode, and once your tests are supposed to start the iOS simulator is immediately available.
28
+
29
+
A full list of UUIDs for iOS simulators is available [here](docs/ios-builds-on-os-x/).
0 commit comments