Xcode 9 repeatedly gives me this error everytime I try to Add Missing Constraints or Reset to Suggested Constraints in a view controller that is attached to a navigation controller.
If I remove the segue connection between the navigation and view controller, adding missing constraints in the view controller works perfectly. This functionality appears to break whenever it is embedded in a navigation controller.
Is there a solution to this bug? I've only seen one other user having this problem on Stackoverflow. I've tested this in three of my Xcode projects and it's barring me from completing any work at all on my apps.
Apparently this is a known bug in Xcode 9. I just downloaded Xcode 8 from the Apple Developer Portal and everything is working fine using that.
https://developer.apple.com/download/more/?name=Xcode
Related
I've been developing a macOS app using a storyboard that defines a main window with toolbar and splitview. It's written in Swift 3 -- I have not migrated to Swift 4 yet. The splitview has a pane for graphics and another for a text log; both scroll. I have view controllers for all three; the two subsidiary scenes are tied to the split view with relationships. This worked up until today when I installed Xcode 9 beta 4. (Yes, I have beta 3 in the trash at the moment and can revert)
Upon cleaning the build folder and compiling, I get the error
NSSplitViewController's 'view' outlet should not point to its NSSplitView; use the 'splitView' outlet instead
However, the NSSplitViewController subclass has no outlets defined (its two children arrange to tell it of their existence in their viewDidLoad methods). Moreover, I don't seem to be able to create an outlet between that window and its controller that would have created the error in the first place.
I now also note that the split drawn in the split view controller's scene is horizontal instead of vertical as it had been. I don't see a way to change that. (I can't run the app, so I don't know if it matters. I suspect it does.)
The net result is that I can't see what the error is trying to tell me. The error prevents the application from building and running, whereas with beta 3 it worked. I'm hoping someone can explain what Xcode is telling me and how to fix it.
I did fix this in my own Storyboard. In the outlets window, I saw that the view outlet was indeed assigned to the NSSplitView. I deleted it. It was also assigned to the splitView outlet, so the change did not seem to effect anything.
The warning went away and my project then did build.
I have no idea if this was always that way and compiler update changed or if this was somehow inadvertently set differently in some way. It makes sense in any case, the NSSplitview should be assigned as the splitView outlet, not the view outlet.
I'm a beginner of Swift and XCode. When I tried to establish connection between a button and a "showMessage" method as is described in this tutorial, the "showMessage" method cannot be found in the pop-up menu.
Then I downloaded the code zip of the tutorial, and run it in XCode. I got error:
"Launch screens may not have triggered segues. (LaunchScreen.storyboard)"
The error storyboard is a main storyboard, not a launchscreen storyboard. Someone may have this trouble because he unintentionally checks "Use as launch screen" for a main storyboard. However, it's not checked in this case.
Where is wrong and how to fix it?
P.S. My XCode version is 8.2.1.
You can not segue through the LaunchScreen.storyboard. Make it through Main.storyboard.
Set one:
check for Use as Launch Screen
and uncheck "Use as Launch Screen"
Set TWo:
check for Is Initial View Controller
and uncheck "Is Initial View Controller"
Set Three:
run your project again.
I am currently learning iOS development and I began with a simple Tabbed Application. It has the default First and Second View in it. I added a TableView with static cells content. I then added another View Controller. I created a Segue using the storyboard. When I set the transition to modal, it works fine. When I set it to push, the app is crashing (Uncaught exception).
Any idea why?
How can I get more information regarding the exception? Can I make the app stops when it encounters an exception?
Figured it out.. I need to add a Navigation Controller to use push...
I have just changed my app to iOS 7 only, and noticed that the Push Segues have changed their animation.
Previously 2 viewControllers animated in/out side-by-side, at the same speed.
But now, the incoming viewController animates quicker, over the top of the slower, outgoing segue.
I cannot find this change reported anywhere. Is it really a change in the OS, or is my app being weird!
Thanks in advance.
The appearance of the navigation view controller’s push animation has changed between iOS 6 and iOS 7: as you’ve noticed, there’s now a sort of depth/parallax effect to the animation. You can see it for yourself in any of the system apps that use a navigation controller, e.g. Settings.
All worked fine in iOS 3.x on the iPad to prevent the Master view of the UISplitViewController from hiding. I created a method SizeControls() that was called whenever the device rotated (WillAnimateRotation event).
Now with iOS 4 on the iPad this no longer works. While the SizeControls is called something is still causing the Master view to be hidden. What do I need to do so that on both iOS 3 and iOS 4 I can have both Master and Details views appear just like in the Settings UI?
Thank you.
Take a look here, apple recommends you show the master view in a popover when in portrait.
If thats not a goer take a look at MGSplitViewController. Its a very nice split view which gives you this functionality for free.