I have just changed my app from supporting iOS 8 and up to supporting iOS 9 and up. I believe I've done this properly, since when I now build my app, I'm getting warnings for everything in the app which was deprecated in iOS 9.
I am using Xcode 9, GM seed.
The problem is that I cannot enable the "Use Safe Area Layout Guides" toggle in any of my storyboards. When I do, I get a warning "Safe Area Layout Guide before iOS 9.0". Is there some additional setting that I need to update? A clean and build did not fix the problem.
Just deselect "Use Safe Area Layout Guides" option, which should fix this.
A screenshot below may point you the right direction.
Hope this image can help
When you changed the deployment target, did it automatically change the deployment target in your storyboard? (File inspector when opening the Storyboard)
Did you update the deployment target in both the Project and in (all) your target(s)?
Project:
Target:
I didn't try quitting Xcode and restarting it before posting to SO! Sorry! The answer is, quit Xcode and try again.
Simple fix.
In file inspector for the view, look for Builds For in Interface Builder Document and in there select iOS 9 and later.
I have been getting this error only on occasion when I work on my storyboard:
Failed to render and update auto layout status for Category
ViewController: IBAppleTVSimulatorAgent.app failed to launch
I usually just close and reopen my xcode and the warning goes away, but could someone please tell me as to why this is happening and how I can have a more permanent solution rather than just restarting my xcode?
Thaaaanks!
It's a glitch in Xcode 7.1 beta 2 when laying out tvOS storyboards. It's just something to put up with until they fix it, hopefully in beta 3.
I was also facing the same issue while developing TV app.
I deleted the Xcode 7.1 beta 2 and
I reinstall the Xcode 7.1 beta 2
this fixed my problem.
I am trying to create a Table View Controller in my storyboard and when I change from "Dynamic Prototypes" to "Static Cells" Xcode stops responding until it eventually crashes.
What I tried so far:
Re-installing Xcode;
Clear Xcode folders under ~/Library (including DerivedData);
Creating in a new project (still crashes);
Ask a colleague to create a Table View Controller with static cells in the same project. He can do it on his computer. I can see the Table View on my computer and even edit rows, but I cannot add sections.
Tried both Swift/Obj-C projects, with or without Core Data;
I am using XCode 6.1.1 (6A2008a), the same as my colleague.
Please help! Thanks!
Yes , I have faced similar problem .please try with Xcode 6.3.x or later version .
Not a fix but may help some. I noticed this was only happening to me when I had two windows of my current project open. Was reworking a storyboard, so I had the old and new side by side. When I closed the windows of my project that I was not currently editing, Xcode did not crash. With more than one window open, editing a Static Table View would crash Xcode EVERY time.
I found a temp Fix. I also noticed that my dock isn't working fine (I can drag and drop things into it or in it). So I rebooted the mac and this fixed the dock problem, I tried quickly in Xcode and it worked. I guess it's something with Mac OS not just Xcode
Using Xcode 5 GM, anytime I switch to the 5.1, 6.0 or 6.1 simulators to test, I get the error "iOS Simulator failed to install application." When I reset the simulator it works, but this is getting very tiring.
Anybody have a permanent fix or workaround?
Looks like this is a known issue. From the Xcode 5 release notes:
After switching the minimum deployment target of an application from
iOS 7.0 to a release prior to iOS 7.0, building and running the
application may fail with the message “iOS Simulator failed to install
the application.”
Go to the iOS home screen, click and hold the application icon, then tap the hovering “X” button to delete the application. 13917023
Another release note:
iOS Simulator
If an iOS app is detached, relaunching the same app from Xcode will
result in a black screen in the Simulator even though the new app is
launched. Terminate the app in the Simulator or relaunch it for the
second time. 14648784
Delete the old version app in your simulator (usually iOS 6.x).
Alternatively, header over to iOS Simulator - Reset Content and Settings.
This can be easier when you have a lot of apps on the simulator and can't remember which one you're currently working on.
You need to do this for every iOS Simulator version that causes the problem.
None of the other suggestions worked for me. However, after comparing my existing app settings to a new vanilla project, I noticed that the "Build" field for my Target was blank. Once I put something in that field, the app installed just fine!
if you have already developed project and you used xib to develop views then
X-Code > Inspector Selector Bar > Interface Builder Document > opens in > and change from Xcode Default(5.o) to Xcode 4.6 .
Build and Run your app it will run successfully, if it won't run again then, header over to iOS Simulator - Reset Content and Settings. delete old app from simulator then Run again.
i got the same problem but solved by following way....
Launch the iOS Simulator
Go and click "iOS Simulator" menu
Click "Reset content and settings"
Close simulator and rebuild your app.
Above screen shot is showing the way how you can do this...
I think this works for you...!!!
Deleting the app in the simulator works for me.
just wanted to add that this happen only if I open xib that created in xcode 4.6
If it's other files, this not happen
try this ....
in my case nothing have worked for me , after resetting the content simulator also , i am not able to install the app on simulator . after that i just changed my project location . i just moved the project to other location . then it installed successfully.
None of the above things worked for me. I just reinstalled xcode and it worked.
Ran into this issue today. Found it was an empty Reference Folder (blue folder) causing this. Removed the folder from Resources in Build Phase... cleaned build folder for the heck of it, and it went away.
/Users/YOURUSERNAME/Library/Developer/Xcode/ --> remove all contents of this folder, then simply launch the app from Xcode.
To check your Executable file settng ex.$(EXECUTABLE_NAME)
(Project setting - info property page)
I have different issue when getting error message “iOS Simulator failed to install application”, the reason is because I have added a property in App-Info.plist without any value. For instance, [Application Category] with no value. Thus the error will show up as well.
When I got this error, the image of the phone actually appeared, but the image of the app I wanted to test did not. Instead, I was on the main page of the phone that shows the apps you have. I fixed this problem by deleting the many icons that appeared on the start screens - about 30 of them. These had been created when I testing apps over the months. So, not saying its a solution, but it started working after I deleted the old app images.
For me it was -framework XCTest.
It made the app die with iOS Simulator failed to install application
and on the device Could not inspect the application package.
Removed it and now works.
You are using Xcode GM which is under beta stage. Use latest Xcode 5.1.1 available.
Also, these error occur while switching between simulator (32 bit and 64 bit).
Quit the simulator and re-build the application. OR
Reset simulator from "iOS simulator" -> "Reset content and settings.."
I changed my app name and bundle id midway. I happened to delete the Executable File name in my plist. I changed it back to "${EXECUTABLE_NAME}" (no quotes) and I'm back in business.
Just upgraded from Xcode 3 to Xcode 4 and built my app, but all I see is a white window. If I minimize the app and open up the app again everything looks good.
I have also tried to just add a simple UIImageView to the window in my appdelegate but I get the same behavior.
I have also tested to just create a new test project and it works as it should.
Any ideas?
I am not exactly sure what the problem could be... but since you say that a new test project works perfectly, the thing I can think of is that you might need to change build/ target settings in ur project by editing your scheme.. try that out...