Xcode 10 - App not updated after building and installing - ios

after the latest update of Xcode 10 I have the problem that when I try to build and install the app to my IPhone 7, Xcode seems to install the app, but I cannot see any changes when I try to change for example a color or a constraint in Main.storyboard.

Try restarting the phone.
Different issue but I was having an issue running an XCUITest on device after upgrading to Xcode 10, and restart solved it.

Quit Xcode and the simulator and then Restart you computer.
If that doesn’t work try using a different simulator.

Related

Unable to run app in Simulator 9.0 using XCode 7.0

When I run my application using XCode 7.0. Everytime I am getting below error. How to fix this issue.
I am using Mac with 10.10.5 . I searched that 10.10.4 later supports XCode 7.0
Please suggest where I went wrong...!
Go to Xcode -> Preferences- Downloads tab. 
Here you will be able to see list of simulator available for downloading.
Download the required simulator.
Restart Xcode
You will be able to run your project on simulator without any issue.
Okay so it seems like the run time components for the simulator are not installed with your version of Xcode (this may have happened when updating or downloading a beta and Xcode got confused).
Try do the Following: Xcode > Preferences > Downloads > Check and Install Now
That should Help, otherwise you can go to itunesconnect or anywhere on the web and download and add the simulator files manually.

Unable to open liblaunch_sim.dylib

Today I have updated xcode. when i tried to run project on simulator(ios version < 9.0) I got this error.
"Unable to open liblaunch_sim.dylib. Try reinstalling Xcode or the simulator runtime.
It ran perfectly on ios9.0 simulator.
here is screen shot. please help me.
This will also occur when you don't have the simulator actually installed within XCode. I recently upgraded to XCode 7.1 and didn't install all simulators and received this same error.
Go to Preferences -> Downloads
Verify you have a checkmark next to the desired Simulator you are trying to run within XCode.
If no checkmark, then install the simulator of choice. 8.1, 8.2, 8.3, 8.4
I don't think that there is an "officially supported" way to solve this yet, but have a look at this answer (which originates from this more detailed troubleshoot) for a potential fix.
[Edit] In you case, try running those:
sudo cp "/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 8.1.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/host/liblaunch_sim.‌​dylib"{,.bak}
sudo ln -sf "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/D‌​eveloper/SDKs/iPhoneSimulator.sdk/usr/lib/system/host/liblaunch_sim.dylib" "/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 8.1.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/host/liblaunch_sim.‌​dylib"
First, find the target file:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/usr/lib/system/host/liblaunch_sim.dylib
You need make backup liblaunch_sim.dylib
Second, copied to destination (Remember to backup)
/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 7.1.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/host/liblaunch_sim.dylib
And If need it to: iOS 8.1.simruntime iOS 8.2.simruntime iOS 8.3.simruntime All done.
Hope it helps.
I faced similar problem this problem occurs when we have multiple versions of Xcode Installed ... So i force quit all the xcode and simulator and then open the xcode version you want to open.

The iOS 8.1 simulator runtime is not available error in Xcode 6.1

I was using Xcode 6.0.1 till now and things were fine. Then I upgraded to Xcode 6.1 and tried running my application(which has a deployment target of 7.0) in iPhone 6 simulator. But it shows an error message :
The iOS 8.1 simulator runtime is not available. Download the iOS 8.1 simulator runtime from the Downloads section in Xcode's Preferences
I manually deleted the earlier Xcode (6.0.1) and installed 6.1 from a dmg.
I tried searching across but couldn't find related stuff. Any help would be appreciated.
It is a Mac problem, not an Xcode problem.
Logout the user, shutdown, restart or just reboot Mac. Your Xcode simulator will go back to normal.
For anyone still facing this issue, this command worked for me:
sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService
Rebooting did not help me.
Installing/Reinstalling Simulators worked!!
Look under (XCode Preferences-> Downloads -> Components)
Maintain an accurate list of iOS simulators
When upgrading, you may drag around old simulators no longer available with your current version of Xcode. You can clean these by running this command in Terminal:
xcrun simctl delete unavailable
Quit Xcode first just for good measures. From the documentation:
Delete a device or all unavailable devices.
Rebooting my computer fixed this exact issue for me. Same error was thrown for both iOS7 and iOS8 simulators. I'm on OS X 10.10 and Xcode 6.1.
Just had this problem with Xcode 8 beta 5. I downloaded ios8 and 9 simulators, but was not able to run my app. I simply deleted derived data and rebooted my computer. It worked for me.

Error opening iOS Simulator with iOS 8 beta version: "Unable to boot the iOS Simulator"

I recently installed the beta of Xcode Version 6 in OS X Mavericks, with which comes the iOS simulator for iOS 8. I've managed to successfully run from Xcode 6 beta on a device with iOS 8 Beta, but opening the simulator always get the same error I have tried to change the hardware version of iPhone 4s, iPhone 5, ... in the simulator and still gives the same error: "Unable to boot the iOS Simulator".
I'm working with Xcode 5.1 at the same time in Mavericks, any suggestion to solve this? Is a possible problem for run this simulator in Mavericks because is only for OS X 10.10? Thanks.
After I found some solutions on the web, a combination of procedures worked for me:
Close Xcode and iOS Simulator (and all related applications)
Install (or reinstall) Xcode6-Beta to Applications folder (direct from the .dmg file)
Open Xcode6-Beta and go to Xcode -> Preferences -> Locations -> Command Line Tools and select "Xcode 6.0" (be sure that you've selected the one in Applications folder)
Launch the iOS Simulator and go to iOS Simulator -> Reset Content and Settings...
Close all the applications and restart your mac (I unchecked "Reopen windows...")
Open Xcode6-beta and test the iOS Simulator
Good luck
I also had this problem and found the solution by doing following steps:
Initially i downloaded Xcode 6 library in Documentation section under the path Xcode --> Preferences --> Downloads and restart my xcode but didn't solve my problem.
Downloaded and installed the iOS 7.1 Simulator under the path Xcode --> Preferences --> Downloads.
Restart xcode again and the problem solved.
I am facing same issue again next morning.
Unsetting the DYLD_INSERT_LIBRARIES variable solves my problem:-
Open terminal and type "sudo vi /etc/launchd.conf" command and press Enter
Press I "Insert" mode and change this
"setenv DYLD_INSERT_LIBRARIES /usr/lib/libimckit.dylib"
to this
"unsetenv DYLD_INSERT_LIBRARIES /usr/lib/libimckit.dylib"
and press esc to exit from insert mode.
Save changes by typing ":wq" Press Enter
Reboot your system and problem soloved.
Prior to that I didn't find any iOS version in front of each listed devices
but after installation or by unsetting DYLD_INSERT_LIBRARIES variable I found the same in front of each device.
I solved by removing and re-adding the simulators see screenshots here.
https://stackoverflow.com/a/25387715/1565615
I don't believe your issue is related to running Xcode 6 in Mavericks, as I encountered the same error on OS X 10.10.
After a bit of toying around with XCode and the iOS Simulator, the only fix I found was simply restarting the computer, and the error hasn't appeared since.
Try a reboot and then see if you can get things up and running.
(On a side note, after restarting just XCode (not the OS), I lost the option to run on the simulator at all—the reboot also fixed this problem, if anyone here encounters anything similar).
In Xcode go to the Xcode menu->Open Developer Tool - IOS Simulators. Choose simulator and then go hardware->device->manage device.
If the troubled device shows in the left column, delete it. Then add the device back from the '+' button. If it wasn't there in the first place, simply add it using the '+' button.
I had previously deleted ~/Library/Developer/CoreSimulator/ directory and the only command that worked for me is xcrun simctl erase all. Perhaps you might want to give this a try.
No need to download a new ios version. All you need is to go to About this Mac > Storage > Manage > Delete XCode Cache. And, it works for me
In latest OS version
About this Mac > Storage > Manage > Developer > select Xcode cache > Click delete button
I've faced same issue and solved by below steps:
1) Move xcode6-beta into application folder
2) Restart mac and open xcode6-beta from application folder.
i too had the same issue, but solved by installing the required simulators (Xcode > Preferences> downloads > install simulators)
This happened to me running the simulator on both Xcode 7 and 8 on El Capitan. The only thing that worked was disabling System Integrity Protection (https://apple.stackexchange.com/a/208481/86757).
I tested an awful quantity of solutions and the only one which worked for me was disabling root protection through Recovery Mode. I tested it with XCode 7.3, it's possible that this approach may work for XCode 8.
Reboot and hold the keys cmd + R prior to show the loading view with Apple Logo
When you are on Recovery Mode, go to Menu and choose Terminal
Type csrutil disable
Reboot the machine and run the simulator again.
I am adding this answer as it seems to be slightly different from the others.
Due to working on an older project I needed to download and run Xcode 7.3 and load the project in simulator - this yielded the "Unable to boot the iOS Simulator" error.
I completed all the above suggestions and none of them worked (reset simulator setting, restarted, deleted and reinstalled Xcode, reset the simulator location, restarted again etc)
In the end the issue was that I was trying to load the iPhone 5 (10.0) simulator on Xcode 7.3.
You can see here the Apple release notes for Xcode 7.3
Xcode 7.3 requires a Mac running OS X 10.11 or later.
Xcode 7.3 includes SDKs for iOS 9.3, watchOS 2.2, OS X version 10.11.4, and tvOS
9.2.
As you can see Xcode 7.3 doesn't include an SDK for iOS 10.0
This meant as soon as I loaded the simulator with iPhone 5 (9.3) it worked immediately.
I would therefore recommend when approaching this issue not to get railroaded (as I did) in thinking that something is wrong with the system before checking the basic things.
Note: It is also worth noting that the simulator must be configured to the Xcode version being used. This can be set in
Xcode -> Preferences -> Locations -> Command Line Tools
and also using the command line:
sudo xcode-select --switch /Applications/Xcode_7.3.app/Contents/Developer
*change the Xcode version to the new one you want to use
one of the reasons could be you might deleted /private folder.
you can try with following commands
sudo mkdir /private/tmp
sudo chmod 1777 /private/tmp
Following are the steps for solved above issue:
Search launchd.conf file in your mac
If not found then create from Terminal with help of command
~ user$ sudo touch /etc/launchd.conf
Terminal will ask you machine password
Then Open created file with help of command for EDIT, if terminal give you error as permission failed
~ user$ sudo /Applications/TextEdit.app/Contents/MacOS/TextEdit /etc/launchd.conf
Open file manually from /etc/launchd.conf (Shift+cmd+g) and enter /etc/ (TextEdit software)
In file "DYLD_INSERT_LIBRARIES" flag replace with "ZZ" and save it.
Restart your machine.
Xcode will defiantly works.
This error indicates an error starting up launchd_sim when booting the simulated device. In and of itself, it does not indicate the actual cause. You can look in ~/Library/Logs/CoreSimulator/CoreSimulator.log for more information about the error (including the error reason).
Possible causes:
On OSX 10.9 and earlier, DYLD_INSERT_LIBRARIES could be set by 3rd party applications. On later versions, invalid DYLD_INSERT_LIBRARIES are ignored instead of resulting in an error.
Usage of older simulator runtime DLC with Xcode 7 betas. Newer versions of Xcode ignore these older DLC.
If you need additional help, please provide that additional datum.
Just check your simulator's iOS version. I fought with this error for 2 days and tried everything. Once I run the project on the simulator with iOS version that my Xcode supports, it worked sadly... :/
I quit everything and restarted the Mac. That's all. Its worked like charm!!
I don't know why, but this happened to me when I had Charles Proxy's throttling turned on.
I didn't have to run Xcode again or clean anything. Just disabling the throttling allowed the simulator to work again.
I also clicked on details, but this was all that I got:
Details
Unable to boot the Simulator. Domain: NSPOSIXErrorDomain
Code 60
Failure Reason: launchd failed to respond.
This might be related a known Xcode 11.2 issue:
Third party “endpoint security” software may cause slow simulators, system freezes, or prevent debug processes from running in simulators reliably. This sometimes manifests as debugserver disconnections or simulator applications receiving a SIGKILL signal. (55853555)
Workaround: Uninstall the third party software.
Though I was seeing this error on 11.1. Yet Apple may have just not realized this was an issue on 11.1 as well ¯_(ツ)_/¯
I have solved this issue using following steps:
Xcode -> Preferences -> Location -> Derived Data -> Delete your project folder.
I got this error on OS Catalina, Xcode 11.
I solved this by simply quiting simulator and Xcode, and then start Xcode and run your application.
1. Quit Xcode and Simulator if running.
2. Remove customised settings setup
defaults delete com.apple.Xcode
3. remove configuration folders
rm -rf ~/Library/Application\ Support/Xcode
4. Quit the terminal and run Xcode again.
Resetting the simulators fixed the issue for me. Run the below
Fastlane command to reset all simulators,
fastlane snapshot reset_simulators
Please ensure you have closed Xcode & simulator before running the command.
Fastlane is an Android & iOS deployment automation tool.
I just simply follow the below steps and the issue is resolved...
Go to About This Mac > Storage > Manage > Developer >
Select Xcode cache > Delete the cache
Now try to open the simulator again and it will work... In case if above steps did not work just try to do the same with s
Late answer, but it maybe helpful to someone. I tried all the solutions provided in this and related posts and neither of them worked.
I am using OSX(version 10.10.3) and Xcode 6.2. To fix this issue I followed the following steps :
Delete all xcode and simulator related files using AppCleaner.
Restart Mac.
Open Disk Utility app from applications.
In Disk Utility app; click on button Verify Disk Permission for your Macintosh HD (there will be some warnings displayed; I think /private/tmp is cause of this issue).
In Disk Utility app; click on button Repair Disk Permission for your Macintosh HD.
Re-install Xcode; now it should work.
More info : How to fix Xcode error ‘Unable to boot iOS Simulator’.
This may helpful
Open simulator with 4s
Click on menu- iOS simulator
Click on Reset content and settings...
Force close the simulator and run app.

Instrument fail to run GUI test script in real iOS device from Xcode 4.4

I have an UI automation script which run perfectly fine before I update Xcode to 4.4.
But after I update Xcode to 4.4, instrument hang after 2nd run on actual iOS device (runs ok on simulator).
Anybody have the same problem and found any work around?
I have seen the same behavior. You don't even need a script. All you need to do is start your app with Instruments, stop recording and attempt to start recording again. I have seen this with XCode 4.4 and 4.4.1 while running the app on iPads with 5.0.1 and 5.1.1.
I fixed this problem.
Here is the solution:
I moved xcode 4.3.2 to trash and had only xcode 4.4.1 installed on my machine.
This works like a gem.

Resources