Running archive in my project in Xcode 11.3 (and 11.2.1 as well) on a fresh installation of Mac OS Catalina results in "Build Successful" but it does not appear in the organizer. My scheme is correctly configured with "Reveal Archive in Organizer" checked.
After searching I found others with this issue from past versions of Xcode who solved it by restarting Xcode/Cleaning/Removing Derived data - this is not working for me. I have also verified my Installation Path is accurately showing /Applications.
I AM able to archive the project using xcodebuild in the terminal and specifying custom paths for the resulting files - but this is not ideal. Any help or advice would be appreciated.
Related
I have a new app which I'm building to be cross platform using SwiftUI
When I build for release I get a very odd error in a popup generated by Xcode.
Unable To Install “nomadgo.ProductivityDashboard”
Please try again later.
Failed to finalize LSBundleWrapper mutator instance for
I only get this error one I build for release. I tried restarting my Macbook.
Specs:
Xcode Version 12.5.1 (12E507)
MacBook Air (M1, 2020) BigSur
The app is fresh project using all latest Xcode settings for cross platform SwiftUI.
I get the error when trying to run the app on my MacBook.
I had exactly same issue. In my case deleting the project from Containers folder and cleaning the project in xCode (⌘ + ⇧ + K) helped.
Just in case, if you are still in this issue even after cleaning builds, check the DerivedData path. The DerivedData path should be somewhere in your Macintosh HD.
Xcode 14.2 (14C18), Mac OS 12.5
My project is running fine in Xcode 11.3 but recently when I upgraded to Xcode 12 app is not getting installed in simulator and showing the error - Could not install at this time.
Failed to get FD to bundle executable....
I suddenly had the same problem, after years of work on the same project across several versions of Xcode and MacOS.
On Xcode 12.4 and MacOS 10.15.5, although everything was working fine, suddenly I got this error popup "Failed to get FD to bundle executable" while trying to Run the project on a(ny) Simulator.
I tried all the proposals I could find online, including changing the Executable Type (which had never changed) or clear the empty env vars defined in the Build settings (there weren't any). Uninstalling/reinstalling Xcode didn't help. Upgrading to MacOS 10.15.7 didn't either. Of course the Apple Support has been of no use at all (they replied with a few general FAQ links about how to use Simulator).
The only thing that worked for me was to checkout the project in a different folder...
The weird thing is, if I rename again my new folder to the initial folder name, it does the error again! It sounds to me like a MacOS bug and/or an Xcode bug.
Error running `xcrun simctl install 95F3A7B0-67B3-490E-B798-D1CBBF813B83 /Users/yakjuly/.expo/ios-simulator-app-cache/Exponent-2.21.3.tar.app`: An error was encountered processing the command (domain=IXUserPresentableErrorDomain, code=1):
Unable To Install “Expo Go”
Please try again later.
Failed to get FD to bundle executable at /Users/yakjuly/Library/Developer/CoreSimulator/Devices/95F3A7B0-67B3-490E-B798-D1CBBF813B83/data/Library/Caches/com.apple.mobile.installd.staging/temp.Nf39ZM/extracted/Exponent-2.21.3.tar.app/Expo Go
Underlying error (domain=MIInstallerErrorDomain, code=4):
Failed to get FD to bundle executable at /Users/yakjuly/Library/Developer/CoreSimulator/Devices/95F3A7B0-67B3-490E-B798-D1CBBF813B83/data/Library/Caches/com.apple.mobile.installd.staging/temp.Nf39ZM/extracted/Exponent-2.21.3.tar.app/Expo Go
I have this problem when I get started with react native.
The issue for me is the file in /Users/yakjuly/.expo/ios-simulator-app-cache/Exponent-2.21.3.tar.app is broken. After I delete this file and re-run the command. it succeeds installing app in iOS simulator.
What solved this for me was the following:
close emulator
clean project and build folder
Shortcut: Command+Shift+K
GUI: Menu Bar -> Product -> Clean/Clean Build Folder
restart emulator
Xcode 13.2.1
The following steps helped me -
1. Select simulator
2. Goto Device
3. Select -> Erase All Content and Settings...
Hopefully, now you will be able to install and run the app on your simulator.
Xcode displays this error every time i run the app on simulator , he forces me to uninstall the app first before every run .
i have 3 .xcconfig files on this project , Is the problem can be related to this? because all other projects are running fine without uninstall.
Xcode is Version 12.0.1 (12A7300)
Try going to Window>Devices and then click simulators. This shows a list of all your simulators. Delete any duplicates.
After that I would look for anything that stands out in your info.plist and in your project under "Build Settings" or "Signing and Capabilities".
These might also help:
iOS simulator: could not hardlink copy. Wrong path in my filesystem?
https://developer.apple.com/forums/thread/67294
I have a problem when it comes to uploading my app to the Apple Store, this is the first time I work with IOS. The Build is working correctly, however, when I perform the project archive (which by the way runs without errors) it does not appear on the Organizer screen so that I can upload the app to the store. I have already created the distribution certificate and the production profile. I already removed the project and added it again, installed an older version of XCODE, tested it on another project but always the same thing.
I am using Quasar / Cordova, version of Xcode 11.3 MAC version Catalina 10.15. In some places I found some people advising to disable the "skip install" property in the build settings, but it also didn't work. Could they help?
I faced same issue after OSX update to 10.15.5
Follow the steps below:
Delete the sub-folders in Archives.
Delete DerivedData folder.
Please perform this steps :
Xcode -> Build Settings -> Installation Directory -> Set value $(LOCAL_APPS_DIR) or /Applicatins
OR
You can open organizer manually also. After successfully archive please perform this steps :
Xcode -> Window -> Organizer
Getting this error for pods in Xcode when trying to run app:
error: A cryptographic verification failure has occurred.
Tried reinstalling Pods/repo
Reinstalling Xcode(s)
Also doesn't run on simulators:
Also, running Sierra at the moment (yes, I know).
This is a regression in macOS Sierra that multiple developers have reported in the forums and in the lab sessions at WWDC. Xcode 7.3 is not officially supported on Sierra. If you want to use macOS Sierra, please use Xcode 8.0 beta or later.
If you must use Xcode 7.3 on Sierra, you can partially workaround this bug by using Xcode.app to install the app through Build & Run, launch the app suspended from the command line (xcrun simctl launch -w booted <app identifier>) and then attach with the debugger and resume the suspended process.
Note that this issue only impact Xcode 7.3.1 downloaded from the Mac App Store. You will not hit this issue if you use Xcode downloaded from http://developer.apple.com (ie, the "drag & drop installer"). Note that you might hit another issue with the same symptoms when using the drag & drop installer. That is discussed in DTAssetProviderService could not start DTXConnection with Simulator
I got mine working now!! Not really sure what I did, at all, but I just deleted the Xcode 8 .app entirely and then I redownloaded it, opened up my project in it, did a pod install and pod update, and it's running in the simulator just like normal! Not sure what I did at all, but redownloading is worth a try, it is in fact possible to fix.
If you have reinstalled CocoaPods so that it updated from a version that is lower than 1.0.0 to 1.0.0 or above it can't hurt to delete your DerivedData folder of the project that is having problems. I don't know why it fixes a lot of bugs when above scenario is the case, but it does! You can do this by going to: Window -> Projects
Then select your project on the left (It was my "Piece" project for me)
Then click the delete button
Hope this helps you out!
Launch "Keychain Access", go to "Preferences..." and click "Reset My Default Keychain". After that I was finally able to build my projects.