I just upgraded to Xcode 13.3-beta, running a flutter project got this error:
Error output from Xcode build:
↳
2022-03-02 17:45:38.148 xcodebuild[62848:6695836] Requested but did not find extension point with identifier
Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in
com.apple.dt.IDEWatchSupportCore
2022-03-02 17:45:38.148 xcodebuild[62848:6695836] Requested but did not find extension point with identifier
Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of
plug-in com.apple.dt.IDEWatchSupportCore
** BUILD FAILED **
Now, I am confused, I am running a iOS app on simulator, why throughs out errors like watchOS?
And I totally don't know how to resolve this error.
Any one could help me?
OK, very weird but running xcrun multiple times seems to fix this. I had also updated to Xcode 13.3 recently.
xcrun -sdk iphoneos --show-sdk-path
The first time it shows the error. The second time it shows the right answer. I ran it with all three sdks, iphoneos, macosx, watchos and all showed the errors the first time. I also ran it with all five of the options for all three sdks:
xcrun -sdk iphoneos --show-sdk-path
xcrun -sdk iphoneos --show-sdk-version
xcrun -sdk iphoneos --show-sdk-build-version
xcrun -sdk iphoneos --show-sdk-platform-path
xcrun -sdk iphoneos --show-sdk-platform-version
The build error from xcodebuild went away after that, although I'm not certain which of the commands fixed it.
Fixed this by running.
xcrun -sdk macosx --show-sdk-path
This outputs your current skd path.
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk
Add this to your .zshrc file.
export SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk
Source it
source ~/.zshrc
Now run
xcrun -sdk macosx --show-sdk-version
To avoid hard coding the version you can add this to your .profile:
export SDKROOT=$(xcrun -sdk macosx --show-sdk-path)
reload profile (source path to your profile) and run
xcrun -sdk macosx --show-sdk-version
to verify
Found solution:
Check for updates of Xcode in App Store (it should be updated
already, but just for confirmation)
Launch Xcode; it will ask you to install additional software. After installation finishes the errors will gone.
If it's a flutter project following step can be helpful:
Update MacOS
Update Xcode and command lines tools
Run flutter pub upgrade, flutter pub get in the project folder
Delete podfile.lock in ios folder of the project
Run cd ios, pod repo update, pod install in the project folder
This is problem from xcode when xcode select doesn't link with CommandLineTools
run below command for link it
// reset to the default command line tools path
xcode-select -r
// Link xcode-select with CommandLineTools
sudo xcode-select -s /Library/Developer/CommandLineTools
If that not working. Maybe problem from the keychain is not unlock.
You need to unlock that by
security unlock-keychain
Or with password
security unlock-keychain -p <password>
Hope this way can help you, thanks.
This issue is sadly with XCode 13.3.
This is pointed out by this answer - Stackoverflow Answer- Flutter for iOS run, build but not archive
The three solutions given were
Modify the code
Downgrade to Xcode 13.2.1
Wait for Apple to modify Xcode
For myself I use CodeMagic, and didn't have the luxury of downgrading my Archive. XCode could take months to update. So modifying the code was the only option. I was able to find this issue opened on March 15th 2022. Which eventually has this solution..
Open your Podfile and paste pod 'DKImagePickerController/PhotoGallery', :git => 'https://github.com/miguelpruivo/DKImagePickerController.git' as shown below:
`target 'Runner' do
use_frameworks!
use_modular_headers!
#Workaround for segmentation fault:11 while archiving
#Add the below line
pod 'DKImagePickerController/PhotoGallery', :git => 'https://github.com/miguelpruivo/DKImagePickerController.git'
flutter_install_all_ios_pods File.dirname(File.realpath(FILE))
end`
Yes I know your error said your errors were through WatchOS. However as I understand, this is an issue that occurs in version 13.3 of Xcode. In Xcode 13.3, if you have a code that uses UI_USER_INTERFACE_IDIOM(), you will get an "Out of Memory" error when you run Archive. Changing "UI_USER_INTERFACE_IDIOM()" to "UIDevice.current.userInterfaceIdiom" resolves the error. Commonly this issue occures with flutter pods using - DKImagePickerController/PhotoGallery.
I was able to fix this without touching anything Watch related. On top of this I made sure my flutter project had a minimum support level of 12, however that might be completely unrelated.
Ultimately downgrading is probably the solution. As well many of my links lead to other solutions if anyone is curious of the diving into it.
There is an error in file /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/Xcode/PrivatePlugIns/IDEWatchSupportCore.ideplugin/Contents/Resources/IDEWatchSupportCore.xcplugindata
You should make its backup, then open it in plist editor and fully remove the following items:
Root/plug-in/extensions/Xcode.DebuggerFoundation.AppExtensionHosts.watchOS
Root/plug-in/extensions/Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS
A workaround that worked for me was to install the previous stable Xcode version 13.2.1 and build it from the IDE.
You can have multiple versions installed, so you don't have to change anything in your current setup.
https://xcodereleases.com/
Check if there is some update for Xcode.
xcode-select --install
If you get the message below from the command above, try:
xcode-select: error: command line tools are already installed, use "Software Update" to install updates
sudo rm -rf /Library/Developer/CommandLineTools
xcode-select --install
Also, you should check if there is a macOS update available.
Click on the Apple icon no top left > About this mac > Software update (for example, macOS Monterey 12.3)
I faced the same problem when updating the project with Flutter 3. After several attempts, the below solution worked for me.
I have deleted the podfile.lock file inside the ios folder and then run the below commands.
flutter pub upgrade
flutter pub get
cd ios
pod repo update > Actually, this was an error for me but ignored it
pod install
Also please make sure you are using the latest MacOS and Xcode.
I hope this will help someone else.
In my case, its React Native app, the problem was with cocoa pods.
Reinstalling pods helped. Run below in your project folder
rm -rf ios/Pods && npx pod-install
Okay, just found a solution which might sound super dumb but updating my Mac OS to Moterey 12.3 solved the issue with no change in the code required.
Got this as well when trying to run the app from Android Studio. Solved this by...
starting XCode,
open the Runner,
run the app from xcode,
stop the app in xcode,
...and then it worked fine to run the app without this error from Android Studio.
I had the same issue , and i could solve it by removing the image picker newer package manually from the package folder and set the image picker package version to image_picker: 0.8.4 , and this solved the issue , hope it can help , maybe if you can share all the error message then i can help you .
you can try install the latest xcode13.3
then you can try xcode-select --install to install the command tools
Run command sudo xcode-select -s /Applications/Xcode.app
Finally, I found solution, hope this helpul for you.
Change flutter channel from stable to master
code#kazus-MacBook-Air ios %flutter channel master
code#kazus-MacBook-Air ios %flutter channel
Flutter channels:
* master
beta
stable
Also experiencing the same issue, I tried #user1503606 and #MCCCS suggestion, sadly didn't work.
Looking at this answer, the issue stems from XCode 13.3 and as #y2ducky suggests, downgrading should solve the issue.
Solutions:
Downgrade to Xcode 13.2.1 (you can find older versions here https://developer.apple.com/download/all/ then expand it and move Xcode (Xcode.app) to Applications folder, which will replace your current Xcode 13.)
Wait for Apple to modify Xcode
Using xcode version "13.2.1" works for me. Seems like "13.3" is doing something differently
Here is another one that helped me to solve this issue. Go to About this mac -> storage and remove support watchOS in Xcode developer settings.
Works with xcode 13.3.1, Monterey intel:
downgrade flutter sdk to Flutter ->2.10.0 Dart ->2.16.0
which can be downloaded here:
https://docs.flutter.dev/development/tools/sdk/releases?tab=macos
change your valid sdk path in terminal with flutter --version
this includes for new projects.
running May 1, 2022
Restart of iPhone solved the problem for me.
I brought another solution.
I tried multiple solutions which mentioned in this question, but all failed.
So, I just tried from flutter starting project. It did build perfectly. After adding some libraries, the library starts to require more higher ios version.
I usually upgrade ios version by Podfile like this,
# Uncomment this line to define a global platform for your project
platform :ios, '12.0'
but, instead of that, I upgraded ios version with Runner.xcworkspace and ios/Flutter/AppframeworkInfo.plist according to this link.
https://docs.flutter.dev/deployment/ios#review-xcode-project-settings
and after that, I finally succeeded to build project.
This also could be a problem with your pubspec.lock file. Some version of libraries probably trying to use Watch Support. That was the my case. So, I fixed some libraries's versions and then it worked fine.
This solution worked for me
Try xcode-select --install
If command line developer tools were already installed try fixing it by
sudo xcode-select -r
After a couple of days of trying all the solutions on the internet. I finally ended up deleting the ios folder inside the project and creating it again using flutter .
then Open Terminal and go to the project and do the follwing.
pub get
cd ios
pod install
And you can run the app now.
It could be this:
Try turning off your Apple Watch. I know... I know. I ignored it for a long time, then dug into the logs, the error messages, researched, etc.
The device name format changes when building when there's a watch involved and can sometimes hang up the Flutter tools because - well, because they're garbage and don't take that into consideration.
I basically just can't use my Apple Watch when I'm building on Flutter (some times), like at all. I have to power it down completely.
After you get a successful build, you may or not be able to turn it back on and have the builds succeed. It's hit and miss.
I get this problem every few weeks, and 100% of the time, it's my Apple Watch being on, changing the build targets that Flutter reads, presumably through Xcode.
** shrug **
In my case it was as simple as a new location added to assets within pubspec.yaml
assets:
- assets/images/
- assets/images/icons # this line broke the whole project because of a missing /
What helped in my case was to run update Xcode CLI to the newest (version: 13.4.0.0.1.1651278267
) which was only displayed with --all --install --force:
softwareupdate --all --install --force
I am following the Flutter Test Drive tutorial on the Flutter Docs. I installed XCode, cocoapods, ran pods setup etc.
However, in Android Studio, when I try to run IOS by clicking "Run IOS Simulator," it opens the simulator but fails to connect.
I also tried doing this from the terminal. Opened an IOS emulator and then ran flutter run in the app folder in terminal. I got an error No devices attached.
Please check whether you installed the latest version of Xcode.
After the installation, try to run the following command.
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
As other people have suggested, it happens when you update XCode. So, run the command in terminal suggested by Muhammed
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
Then, you probably have to run
flutter clean.
For it to run properly.
I ran into the same problem but unfortunately, #MUHAMMED IQBAL PA's solution didn't suffice.
Running these two commands, however, resolved the problem:
As pointed out by others:
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
:
sudo xcodebuild -runFirstLaunch
I fixed this problem by flowing these steps and refreshing the list of simulators
This error showed up after I updated my Xcode.
Open Terminal
Run the following command in Terminal
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
Enter your device's password.
Your IDE (Android Studio or IntelliJ) will detect the IOS Simulator as soon as you click return.
it happened to me when i have updated my Xcode, use this command to let Flutter recognize your Xcode again.
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
I have to use three steps:
running this two commands :
1)
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
2)
flutter clean
3)
I have to select on Android studio Ide - (on the simulator select button drop down left hand side of main.dart showing) I have to select "Open IOS emulator".
Then the simulator run. And the simulator was Auto select on the emulator selected section.
I have used Android Studio Bumble Bee and Xcode 13.
The summary is, I think, I have to open the simulator first, then its come to online with Android studio.
I came across this problem on my MacBook.
iOS toolchain - develop for iOS devices (Xcode 8.2.1)
✗ Flutter requires a minimum Xcode version of 9.0.0.
Download the latest version or update via the Mac App Store.
Xcode was not updated. That is why IOS simulators are not supported.
Also make sure that you have agreed to Xcode licenses via running the command,
sudo xcodebuild -license
I Fixed this issue like this:
Open simulator
Go to "Device" in menu
Click "Erase all content and settings"
which this will delete all content and settings of the simulator but the problem of hide in the android studio devices will be fix.
I had different issue why IOS simulator was not appearing in fresh installation - dart sdk was not configured. I've clicked run->run there it was showing that dart is not configured, I've added flutter/bin/cache/dart-sdk in config and after that iphone simulator has appeared. Of course I followed other steps:
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
sudo xcodebuild -runFirstLaunch
I am trying to compile a Kivy program onto iOS, but when I run the command to build the Kivy distro I keep getting this error:
xcrun: error: SDK "iphonesimulator" cannot be located
I have xcode on my computer. What is going on?
A bit late, but I had the same error experimenting with kivy and this helped me:
Open in XCode Preferences, tab into Locations and take a look at your Command Line Tools selection. Mine was empty. When I changed it to the current used version suddenly the error was gone. I found this solution here (bottom): https://groups.google.com/forum/#!topic/rubymotion/Xw8gPcr2Fl8
If there is still something missing you can try to download an older IOS version to be sure there is something installed. Next to your appname you can select the device, click on it and select Download Simulations... and select the IOS you wish. I have done this step before the above, so I don't know if it's necessary.
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer/
reason: if you download the xcode more than one version . the path is not only one....
It fixed for me once I downloaded the previous version of the simulator in my local.
I'm trying to upload a release to Fabric & I'm getting errors as follows. I'm using the Xcode 6.3 (recently updated).
Xcode: 6.3
Fabric: 1.1.3
OSX: 10.10.3
What should I do to resolve above error & continue uploading the release via fabric desktop tool?
Is there any other way to upload binary to fabric?
Mike from Fabric here.
1) To clear that error from Fabric.app: Quit Fabric.app, then run this command to clear the local cache:
rm -rf ~/Library/Caches/com.crashlytics.mac
You may also need to clear:
rm -rf ~/Library/Caches/com.crashlytics
rm -rf ~/Library/Caches/com.crashlytics.data
rm -rf ~/Library/Caches/com.crashlytics.run
Then restart Fabric.app and you'll be all set!
2) To distribute outside of Fabric.app, use either method mentioned here.
If you have multiple versions of Xcode installed on your system you may need to ensure the command line tools are set for the version of Xcode you're attempting to build from.
Navigate to "Locations" in Xcode preferences (select Xcode from the menu bar, then "Preferences..." then "Locations"). In the drop down next to "Command Line Tools:" select the version of Xcode you're using and then attempt a build.
I had this problem because I have 4 versions of Xcode on my mac, and none of them are named simply 'Xcode'. So, I changed the desired version name from Xcode8.1 back to Xcode.
This part might not apply to most people: If you're using the xcode-select tool (you should if you have multiple versions of xcode on your computer) then you need to make sure xcode-select is pointing to the correct version with the correct name.
The solution for using Xcode beta version
I assume this is due to archive in Xcode beta and the path location does not match. Of course, I experienced this and it worked. Just do this step:
sudo xcode-select --switch /Applications/Xcode-beta.app/
And do upload to Fabric again.
OMG, what I've done?
Couple of days ago, I tried using macport to install something, because I'm using Xcode 4.3 and the command-line tool hadn't been installed by the time, macport wouldn't work. So I followed some guide to get command-line tool installed, then I used following command:
sudo xcode-select -switch /Applications/Xcode.app/
which I think screwed everything except macport: now, in Xcode, even a simple single-view iOS project won't be compiled, it says "UIKit/UIKit.h not found".
Does anyone know how to correct this? I don't want to re-install the gigantic Xcode again, gotta do some iOS project tonight, help!
You should be pointing it towards the Developer directory, not the Xcode application bundle. Run this:
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
With recent versions of Xcode, you can go to Xcode ➙ Preferences… ➙ Locations and pick one of the options for Command Line Tools to set the location.