-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make iOS 15 SDK and runtime available to engine builders #85555
Comments
Having trouble uploading a second Xcode cipd package with the same version. Filed https://bugs.chromium.org/p/chromium/issues/detail?id=1225115. |
That package didn't work, it had |
Hmm, the framework is trying to be built with the latest SDK, I guess that isn't pinned to iOS 14 somewhere:
Which is causing it to hit dart-lang/sdk#46499. |
dart-lang/sdk#46499 is fixed, let's see if this passes: Next step is to investigate why
|
Hmm, they both passed this time. |
Double checking by re-downloading the properties and trying again: |
Those passed. |
|
The Xcode 13 toolchain is available on CI now we should definitely proceed on unblock this as it will hinder use of newer APIs. @jmagman Do you believe we should file bugs for the individual work issues you identified or are they all minor enough that we someone can attempt to track and fix these in one go? |
Do you mean the cipd package I uploaded? It doesn't work yet, it's missing some simulator runtimes, and more importantly, the version of clang enforced by We need to keep the builders on a version of clang older than or equal to the version enforced by the This will become much easier once #91689 is done, right now it takes many hours to validate. |
This one might go away when I upgrade the builders to the version of clang in Xcode 12.3 #84453 (comment), I need to check though. |
For some reason, the
But the devicelab staging builders using the same Xcode cipd bundle show available runtimes, and tests are passing on simulators:
https://luci-milo.appspot.com/p/flutter/builders/staging/Mac_ios_staging%20flavors_test_ios/679 @godofredoc are you aware of any additional Xcode/simulator/caching priming the devicelab recipes do that the engine do not? |
The failing engine builders do not even show |
The linked task ran on a devicelab machine. Devicelab downloads xcode once and caches them indefinitely. Does running the task on a different devicelab machine works properly? |
It's passed on |
@godofredoc When I download the cipd bundle I only see the iOS 15 simulator runtime in I bet Or we need to do #91689 to get the necessary runtimes installed. |
Actually that particular test is only building the app, not running tests on the simulator.
I don't understand why
|
Filed #94780 |
I believe #91689 is the last piece to getting the tests to pass. |
any update? |
🙂 |
Any update on this? Reaaalllllyyyyy need flutter/engine#29797 to be able to be merged sometime soon here |
We hit an issue running web tests on the version of macOS needed by the newer version of Xcode, working on upgrading the version of Chrome here #98278. |
looks like it was closed |
The framework builders have been updated to Xcode 13 as of #98297 Found a new clang error introduced since the last time I tested this in January #99795 We're working on getting the builders to be able to cache multiple versions of the iOS simulator runtimes #99698 Once all the tests in flutter/engine#31915 pass we can merge it, and that will make the iOS 15 SDK available and will close this issue. |
Clang issue resolved. Caching multiple versions of the simulator also resolved. |
iOS 15 SDK and simulators are available in the engine as of flutter/engine#31915 |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Xcode 13 beta 2 is now available on go/xcode. Add the iOS 15 SDK and simulator runtime to the Xcode
12a7209
cipd package and reupload.This will allow the engine to start implementing new iOS features, and to test them on the simulator.
See go/xcode-at-flutter.
The text was updated successfully, but these errors were encountered: