Repository navigation
Engine roll causing failures in building an iOS on mac #71496
Copy link
Copy link
Closed
Labels
P0Critical issues such as a build break or regressionCritical issues such as a build break or regressionengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.
Description
Roll attempt: https://github.com/flutter/flutter/pull/71480/checks?check_run_id=1480497561
Error: https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20build_gallery/3153/overview
Error output from Xcode build:
↳
** BUILD FAILED **
Xcode's output:
↳
note: Using new build systemnote: Planning buildnote: Constructing build descriptionerror: unable to resolve run destination SDK: 'iphoneos13.0' (in target 'Reachability' from project 'Pods')error: unable to find sdk 'iphoneos13.0' (in target 'Reachability' from project 'Pods')error: unable to resolve run destination SDK: 'iphoneos13.0' (in target 'connectivity' from project 'Pods')error: unable to find sdk 'iphoneos13.0' (in target 'connectivity' from project 'Pods')error: unable to resolve run destination SDK: 'iphoneos13.0' (in target 'integration_test' from project 'Pods')error: unable to find sdk 'iphoneos13.0' (in target 'integration_test' from project 'Pods')error: unable to resolve run destination SDK: 'iphoneos13.0' (in target 'url_launcher' from project 'Pods')error: unable to find sdk 'iphoneos13.0' (in target 'url_launcher' from project 'Pods')error: unable to resolve run destination SDK: 'iphoneos13.0' (in target 'Pods-Runner' from project 'Pods')error: unable to find sdk 'iphoneos13.0' (in target 'Pods-Runner' from project 'Pods')error: unable to resolve run destination SDK: 'iphoneos13.0' (in target 'Flutter' from project 'Pods')error: unable to find sdk 'iphoneos13.0' (in target 'Flutter' from project 'Pods')error: unable to resolve run destination SDK: 'iphoneos13.0' (in target 'device_info' from project 'Pods')error: unable to find sdk 'iphoneos13.0' (in target 'device_info' from project 'Pods')error: unable to resolve run destination SDK: 'iphoneos13.0' (in target 'video_player' from project 'Pods')error: unable to find sdk 'iphoneos13.0' (in target 'video_player' from project 'Pods')error: unable to resolve run destination SDK: 'iphoneos13.0' (in target 'Runner' from project 'Runner')error: unable to find sdk 'iphoneos13.0' (in target 'Runner' from project 'Runner')
════════════════════════════════════════════════════════════════════════════════
Building a deployable iOS app requires a selected Development Team with a
Provisioning Profile. Please ensure that a Development Team is selected by:
1- Open the Flutter project's Xcode target with
open ios/Runner.xcworkspace
2- Select the 'Runner' project in the navigator then the 'Runner' target
in the project settings
3- Make sure a 'Development Team' is selected.
- For Xcode 10, look under General > Signing > Team.
- For Xcode 11 and newer, look under Signing & Capabilities > Team.
You may need to:
- Log in with your Apple ID in Xcode first
- Ensure you have a valid unique Bundle ID
- Register your device with your Apple Developer Account
- Let Xcode automatically provision a profile for your app
4- Build or run your project again
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P0Critical issues such as a build break or regressionCritical issues such as a build break or regressionengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.
Type
Projects
- StatusShow more project fieldsTo be archived
Activity
jmagman commentedon Dec 1, 2020
@godofredoc is this #70793?
godofredoc commentedon Dec 1, 2020
yes it is the same, retrying should fix the problem long term solution requires creating our own xcode packages.
godofredoc commentedon Dec 1, 2020
Setting as a P2 as retrying will pass the build.
chinmaygarde commentedon Dec 7, 2020
Closing this as a duplicate of #70793
github-actions commentedon Aug 9, 2021
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
flutter doctor -vand a minimal reproduction of the issue.