To select this Stack you just have to open your app on bitrise.io,
go to the Workflow tab (Workflow Editor), and on the Stack tab select the Xcode 11.2.x
option and your next build will start on the Xcode 11.2 stack. Note: you can now select separate stacks for separate workflows!
Read more at: https://blog.bitrise.io/per-workflow-stack-selection-is-here.
This new Virtual Machine replaced the previous Xcode 11.2.x configuration,
so if you’ve already selected the Xcode 11.2.x stack for your app, you’re automatically using Xcode 11.2 (final) now.
You can find the changes/updates compared to the Xcode 11.2 beta2 stack here:
If you use CocoaPods and you pod install during the build in your project you might want to wait just a bit before switching to the Xcode 11.2 stack.
What happened is that the latest cocoapods version (1.8.4) which is installed on the stack by default no longer downloads the cocoapods spec repo when you do a pod setup, only at the very first pod install.
Practically this means that your build will take about 8 minutes longer if you use cocoapods on Xcode 11.2 stack.
We’re working on a quick fix for this issue which should be out later today - will post an update here once that’s done.
Fix applied on the current Xcode 11.2 stack VM images, basically we ran pod repo add master https://github.com/CocoaPods/Specs.git on them and then saved it as a new base VM, so build VMs created from these base VMs now include the default cocoapods spec repo by default.
We’ll work on a longer term fix to prevent future regression.
We’re getting errors now with Xcode 11.2 when submitting to iTunes Connect:
Deprecated Xcode Build. Due to resolved app archives issues, we have deprecated Xcode 11.2 on November 5, 2019. Download Xcode 11.2.1 or newer, rebuild your app and resubmit.
Any idea when Xcode 11.2.1 will be available on the Xcode 11.2.x stack? Thank you so much!
Looking on system report, there seems to be multiple Swift version.
L247~276
=== Checking Xcode CLT dirs ============
* ls -1 /usr/include/CommonCrypto
ls: /usr/include/CommonCrypto: No such file or directory
* ls -1 /Library/Developer/CommandLineTools/
Library
Packages
SDKs
usr
* /Library/Developer/CommandLineTools/usr/bin/swift --version
Apple Swift version 5.0.1 (swiftlang-1001.0.82.4 clang-1001.0.46.5)
Target: x86_64-apple-darwin18.7.0
========================================
=== Xcode ==============================
* Active Xcode Command Line Tools:
/Applications/Xcode.app/Contents/Developer
* Xcode Version:
Xcode 11.0
Build version 11A420a
* /usr/bin/swift --version
Apple Swift version 5.1 (swiftlang-1100.0.270.13 clang-1100.0.33.7)
Target: x86_64-apple-darwin18.7.0
We are aware of the current breaking change in the AppStore submission processes and our Infra team is working on updating our Xcode 11.2 stack to Xcode 11.2.1 so that you can have a seamless transition to the new system that allows you to submit your app to the Store. The ETA for this release is sometime today! We’ll make sure to update this thread later today once it’s in production,
hi @wn_muta, it is expected, present because Xcode and the Xcode CLI is using different version of Swift. Your builds will be using the latter one (5.1 in this case) not the CLI version.
