This is on watchOS 4.3 beta (15T5165e) and Xcode 9.3 beta (9Q98q), but I don't think it's because of them being in beta because another WatchKit project ran on device just fine. I have tried unpairing/repairing, restarting the iPhone/Watch/macOS/Xcode (while making sure to to tap "trust this computer" on the watch) but Xcode still says "Running" in the WatchKit scheme without actually installing and running the watchOS app, eventually saying "Watch app launch timed out."
Disable WiFi on the iPhone. This helped me.
I came to this after following #Appyx advice to activate a hotspot on iPhone. Then I noticed, that in hotspot mode WiFi is automatically disabled and tried this.
Related
I updated to the latest AppStore release of Xcode (12.3, 12C33).
It worked fine for an hour or two. After that it started to constantly freeze after being open for a few seconds to minutes.
I've tried the following, all without success so far:
restart macOS
clear derived data
tried with different projects
updating to latest macOS 11
Any other ideas or suggestions how to fix this?
Update
I can confirm that this is fixed in Xcode 12.5
I found an answer by Darr on the question "Xcode freezes after upgrade to 12.3" on Apple's developer forums that worked for me:
Unpairing my device connected via network and using only lightning cable seems to have resolved the issue for me.
Xcode > Window > Devices and Simulators > device > Connect via network
After going mad, I fixed this by removing all devices from Devices and Simulators (I had connect via network activated).
For now, it's working fine.
Power off your Apple Watch
Xcode may hang if the host Mac is connected to an iOS device which has one or more companion watches. The hangs occur when the watches aren't fully prepared for development, or if they are experiencing poor wireless connectivity. (72490921) (FB8945320)
Workaround: Power off the watches, or unpair them from the iPhone.
Xcode 12.4 Release Notes
You can force Xcode to freshly prepare a watch for development using these steps:
Force-quit Xcode.
Power-off and disconnect all iOS device from the Mac.
Reboot the Mac.
Launch Xcode, close all projects, and open the Devices and Simulators window.
Power-on and unlock an iOS device and its companion watchOS devices by entering the passcode as required.
Plug the iOS device into the Mac using USB cable.
Check each iOS device and each watch for any pairing request and approve the requests.
Monitor the status of device preparation in the Devices and Simulators window. If Xcode presents device-preparation errors, follow the guidance in the error message to resolve the error.
Once Xcode finishes preparing the iOS device and its companion watches for development, repeat steps 5 through 8 for each remaining iOS device and its companion watches until you verify that Xcode has prepared all devices for development. You may now open your Xcode projects and resume development.
I've been having the same problem. I had an iOS device connected via USB, unplugged it and it un-froze. Then I continued to have issue requiring force close each time.
I then clear derived data and things have been fine. I opened a StickerPack project and also had the same issue. Clearing DerivedData also fixed it.
Clear Derived Data:
Xcode pulldown menu > Preferences > Locations tab
Click the little arrow next to the path under Derived Data.
Delete the entire folder for you project. It will look like "MyAppName-bwonddotztrgkkfexrjxoncvmjit"
See this explanation about whether it's safe to delete DerivedData for your project.
I had the same problem with appstore version and someone advised to install from site, now it works fine. https://developer.apple.com/download/more/
Disable WLAN on my iMac fixes the problem currently.
Hope they will releast a fix very soon.
Xcode 12.3 is unstable and many times it crashes.
I reverted back to Xcode 12 and copied disk image of 14.3 in Device Support folder of Xcode (Contents > Developer > Platforms > iPhoneOS.platforms-DeviceSupport).
This I needed to debug on iPhone device having version iOS 14.3
https://github.com/mspvirajpatel/Xcode_Developer_Disk_Images/releases
I recently had similar situation. My Xcode 12.3 project could not be opened. I tried to open directly from popup that appears on start of the Xcode.
What worked for my was to downgrade Xcode to 12.2 and launch Xcode on new project. And then click my old one.
Maybe it would work without downgrading but I didn't check.
I had this problem too. I fixed it by going Devices and Simulators in the Windows file and disconnecting the iPhone reference I had for my phone when testing and app. Since the phone was no longer connected, its presence seemed to create a freeze.
In my case XCode 12.5 hangs/freezes on startup more or less instantly, right after it opens kind of an empty workspace.
I removed everything that I could imagine that deals with XCode on my machine, but it didn't help.
At the end I just used the hotkey for "Close Workspace" - Ctrl+Alt+Cmd+W
I hit this combo very often, very fast right after opening XCode and it worked!
The strange empty workspace showed up and closed instantly - now I could select other projects and everything works again.
There could be the multiple reasons and in my case reason was source control
preferences > Source Control > uncheck Enable source control
I have these performance problems with the newly updated Xcode from the AppStore to 12C33 (Xcode frozen for many seconds, instability of interface builder, etc.) only with apps which have frameworks added with cocoa pods and when working in the xcworkspace-file. (Integration of frameworks with Catharge even fail with error message 65). I'm running Xcode under macOS Catalina. Don't know what the technical reason could be, hence would appreciate if someone has an idea on this how to fix it.
Update: In the meantime I could fix it:
I eliminated my own devices from the device list and did then a deintegration and a new install of the cocoa pods for the projects. Afterwards I setup my devices again in the device list and all worked well again. Only eliminating and reintegration of my devices as described above didn't work in my case.
Xcode "Run" operation fails to install a watchOS app on a real Apple Watch device with error description:
The host is not paired with the device.
Context:
First time ever trying to install a watchOS app from Xcode onto an Apple Watch device for testing/debugging
The watchOS app is an official Apple SwiftUI tutorial example
Assume latest versions of MacOS, Xcode, watchOS, Watch device, etc.
The selected scheme is the watchOS app target
The selected device is "[my Apple Watch name] via [my iPhone name]"
The Apple Watch is in fact paired with the companion iPhone, despite what the Xcode error says
The Apple Watch has not yet trusted this particular Xcode, Mac, developer account, or app. The Apple Watch should have received a "trust/don't trust" notification, but did not; this may be a bug on Apple's part.
However, we can force the notification to pop up by simply restarting the Apple Watch device. The Watch should receive the notification immediately upon restarting. Click "Trust" in the notification on the Watch. Then retry, from Xcode, the "Run" operation. The watchOS app should now install OK on the Apple Watch device.
What needs to be done is restarting both devices, iPhone and paired Apple Watch, connect iPhone to computer with cable. When the trust/don't trust notification appears on the Apple Watch or iPhone obviously choose 'trust'. Then the app will install again.
What it stops from running on your watch sometimes is if you have a simulator debug session open still. It says it can't install because there is another debug session running (but not on your watch..)! Closing this simulator session will allow you to install on your watch.
Other times xCode is building fine and thinks it's running the app on your watch, but it runs an old version and you don't see any changes made. Then you have to delete the app from your Apple Watch.
What also sometimes stops it from running on the Apple Watch are in Xcode the Preferences->Accounts->Profiles. Installing them manually will help in that case.
If nothing works uncouple your apple watch from your iPhone and recouple again.
Why isn't this still been resolved? I see people complaining about it for several of years now. Is this bug only related to standalone apps?
I am trying to pair my apple TV (4th Gen) running tvOS 11.1 with Xcode 9. After entering the pairing code, Xcode tries to setup the Apple TV for wireless debugging and enabling development mode, but fails with the error
"An error was encountered while attempting to communicate with this device. (End of file.)" See below image
Note that I was able to pair with my apple TV successfully and run an app on it couple of weeks ago using Xcode 9 wireless debugging feature. Wireless debugging works fine for iphone and iPad. Now, I seem to be having problem with my Apple TV.
UPDATE: Now I have tried even resetting my AppleTV, still same issue.
Xcode 9 Devices and Simulators Window
I have tried restarting my apple TV and tried reconnecting it with Xcode multiple times, but I get the same error always.
Do I need to reset my apple TV or is there any other work around available to fix this issue ?
As it turned out, I had to use Xcode beta version, as I was installing app on the beta tvOS version. I didn't notice that Apple TV was updated to tvOS 11.1 which is in beta at the moment.
Solution: Using Xcode 9.1 (beta) to install the app on Apple TV 4 worked perfectly.
Xcode gives me this message every-time I try running my app on my iPhone. (Works fine on the simulator.) (And this occurs in every project I have.) (I also just downloaded Xcode again.)
This is the message I get.
App Installation Failed.
Unknown Error Occurred.
How do I fix this error?
Unplugging iOS Device and plugging it back it in fixed it for me.
Alright, it was a simple fix:
Go into Xcode Preferences -> Accounts -> More Info. Hit the refresh icon.
Clean your project. Project -> Clean.
Force quit Xcode.
Reboot Mac and Device.
If you have the same App but downloaded from AppStore, I suggest to remove the App manually from your device, then try to run the new version with XCode.
After following the suggestions in this thread (restarting iPhone, cleaning Xcode project, quitting and re-launching Xcode) and others (setting Team to None then back to my Team) and unplugging and replugging Lightning connector from my iPhone 6 I was still experiencing this problem. Xcode would even display an error that my iPhone 6 was locked, even though it was not.
I was able to fix it by unplugging the USB-A connector of the USB to Lightning cable from my MacBook Pro, then plugging it back in. I'm not sure why that made the difference, but glad that it did resolve this annoying problem.
I have this issue regularly. There are a number of techniques that help me overcome it, including the classic "turn it off and back on again."
One thing that isn't mentioned here is that the iPhone should be switched on, unlocked, connected to the mac and then the app should be run (with the iPhone unlocked). Don't lock it!
Make sure your device name doesn't have any emoji (Xcode 11.0)
if you using vpn services, then you need to turn off vpn. Works for me
I have been having this Xcode problem for a couple of months where my iOS simulator stops working whenever i run any application on Xcode and says, "The simulated application quit." and "iOS Simulator could not find the SDK. The SDK may need to be reinstalled." I am running Xcode 4.3.3 and have iOS sdk 5.1 and everything updated but it happened on my previous version of Xcode also. I have tried reinstalling Xcode over 10 times now and have been posting this question for a while now. No one has been able to get a solution. I have even sent in a bug report to apple but i don't think they will respond. I have tried doing everything every other person that has this problem has been told to do in other threads. I'm honestly thinking about just buying a new mac and seeing if Xcode will work on that one or taking in my current one to get looked at by apple. So if anyone has any ideas please let me know.
Go to Xcode -> Preferences -> Downloads and make sure the "Target SDK" you have selected in your project is in fact installed under the Downloads windows. For me this magically was uninstalled. Once i installed the SDK that my app was using, all worked again
This worked for me: http://www.colinbowern.com/posts/the-simulated-application-quit
I just deleted the folder "6.1" under ~/Library/Application Support/iPhone Simulator
The I just launched again the app and the simulator recreated correctly the 6.1 folder.
Resetting the simulator settings (iOS Simulator > Reset Contents and Settings) resolved this issue for me.
I had the same issue. For me suddenly all the installed simulators (4.3 through to 6.0) stopped working. I then went to Xcode -> Preferences -> Downloads, and there I had the chance to update at least the 5.0 simulator. This is now working, yet I was not able to get the 4.3 or 5.1 or 6.0 to work.
I have personally experienced a weird thing with xcode regarding this issue. Sometimes the sdk is installed properly but it still gives this error. I have two classes, if I call first class from the app delegate then the ipad simulator works fine but when I call the second class then it gives the error that the sdk needs to be re-installed.
In my case when the error occured, I had two errors in the second class. When I corrected the errors after debugging, the ipad simulator started to work completely fine. This is quite weird but its not the problem with your sdk, the problem is somewhere in the code.
This just happened to me. I tried to launch with iPhone 5.1 Simulator, got the error "iOS Simulator could not find the SDK. The SDK may need to be reinstalled." I tried running iPad 5.1 Sim, which worked. I switched to non-retina iPad. Then I tried running iPhone 5.1 Simulator again, and it worked.