Xcode = "Unassigned Children" error:
(Xcode 14.1, 14.2)
I've begun with the treatises presented in great numbers throughout SO.
Initially, it looks solved with "Individual Scales", until I change from Individual Scales to Single Scale, whereupon the "Unassigned Children" re-appears.
I have dragged the Unassigned images UP TO the Individual Scales which temporarily helps UNTIL I switch Scales as just stated.
I have also selected the unassigned image(s) and deleted via delete button. Clean and Build. NO HELP.
It's obvious that this error would cause my iOS App to be rejected.
So, what am I doing wrong?
Appreciate it.
Related
I have a problem to remove a warning. I added a search bar into my viewController, everything is working fine but i recieve this warning:
I updated all constraints + the position and it disappears but after reopening my project, the warning is still there. I tried every clue.
I need help please.
If you click the yellow warning indicator on the right side of the Category Table View Controller scene, you will be able to select an Xcode recommended fix for your warning (in this case you want to select the update frames option).
I have a huge app in process, and since updating to Xcode 7.3, doing anything in storyboard is like molasses!!
About a month ago, I had about the same speed using one HUGE storyboard, so I split the project up into 5 separate storyboards, and Hallelujah, a hundred times faster!
But now, after updating, even dividing to 7; slow as can be!
I'm about to back up, then try and recreate one big one, then back up again, then divide again - to see if that does anything; but I am doubtful.
Anyone know how to fix this, or what is wrong with the latest update?
Well, not a great solution but, all I can determine is that; if the number of items and constraints in the view gets over a certain amount (using Xcode 7.3), the speed suddenly drops horribly.
So what I ended up having to do with this last storyboard (8 of 8) is to take a slide out side pane full of buttons and subviews, and place it in a container view - so that I could give it its own VC and thereby make it a stand alone 9th storyboard.
Not a great solution that's for sure, especially since I had to tie all of the buttons and methods to the parent view controller. I was lucky in this event in that the parent view (my main app map) is a single instance occurrence so I was able to reference it at launch, and merely prefix my former methods with the reference. If this was not so, I guess I would have to have done some serious protocol / delegation.
So, a proper solution (or 'fix' if it is Xcode's doing) is still wanting :)
I cannot find any reference to this on SO.. The full message is:
"This application is trying to draw a very large combo box, 32 points
tall. Vertically resizable combo boxes are not supported, but it
happens that 10.4 and previous drew something that looked kind of sort
of okay. The art in 10.5 does not break up in a way that supports
that drawing. To avoid breaking existing apps, NSComboBox in 10.5
will use the 10.4 art for large combo boxes, but it won't exactly
match the rest of the system. This application should be revised to
stop using large combo boxes. This warning will appear once per app
launch."
Any ideas what to do about it?
I made the box in IB, and don't think I did anything special to create it.
I had this same issue. The combo box was in a cell in a table. I changed the row height setting of the table to automatic. But, this gave me an error for not being a valid setting for a cell based table. However, when I reset the table's row height to fixed, the message went away.
More Google searches seem to indicate that this has something to do with the height of the combo box. In my case, the row height of the table increased when I reset it from "Automatic". Perhaps this will give you something to go on.
I had the same error. When I dragged comboboxes out of a Stack View, Xcode messed up their heights. To correct the problem, I added height constraints of 22 to each of them. That caused the warning. When I deleted all the height constraints, the warning went away. The comboboxes didn't revert to the crazy heights they had when I dragged them out.
I've had this forever, but ignored it because I had no idea why it was happening.
From reading the other answers here...
From the storyboard I edited the Combo Box Cell inside the combo box. I changed the Cell Size from Regular to Small and back to Regular.
The problem went away.
I am currently updating my app, and I have been facing a very strange and complex problem for the last few days. The part of the application that is problematic is made of one UITableViewController that is a list of news, and (after you click on a news) a detail view which is in fact a UICollectionView with as many details CollectionViewCells as there are news.
Each of these can have an infinite amount of elements, and are loaded 20 by 20 when the user scrolls to the bottom of the TableView (or to cell that is at the furthest position right on the CollectionView). Also, inside a DetailsCollectionViewCell, there can be another UICollectionView, containing images.
My problem is that after scrolling a few details views, after behaving normally (ie memory is allocated when I change the page, then stabilize until I change the page again, and so on), the memory allocation start to ramp up slowly but steadily, even if I stop doing anything at all. Also, the CPU usage will go to 100-120% and stay there, whatever I do, even, again, if I don't touch anything. After a while, the UICollectionView and the UITableView will not render any animation anymore, thus loosing the paging, and the inertia when scrolling, and overall resulting in a very poor user experience.
The strange thing is, I can observe these behaviours via XCode 5's Debug Navigator, but when I try to use instrument to find the source of the leaks/allocations, the allocation graph is normal, and I get 40-60 MB mem usage, no more, despite still observing the animations/paging problems.
Has anyone already met such a strange behaviour, and can someone help me in finding the cause of all this fuss ? (maybe by fixing Instruments ?)
Thank you all in advance, don't hesitate to ask me for more infos if needed !
I found the solution to my problems in the meantime.
About the difference in Memory usage between Xcode 5's Debug Navigator and Instruments, it was caused by my use of NSZombies. I have the habit of always setting them on, and that just flew off my mind... To remove them : Product > Scheme > Edit Scheme > Diagnostics > Enable Zombie Objects (just unmark it).
The cause of my CPU usage was an animation that was going on indefinitely in the background on multiple pages. The solution was to first of all stop it as soon as it is not seen/useful anymore, the optimise it by changing my approach (I was using CAAnimation and moved on to using UIView's animate function).
I think I might have pulled the trigger a bit too fast here, but hey... if this can help someone later, then it will not be a waste !
I just noticed the strangest thing when updating one of my Mac applications.
The menu bar of the application when run has different font sizes (!?). Some items are in the normal system text size (13 point?) and others are a few points smaller (11 points?). What gives?
I didn't even know that you could do this.. never mind understanding how this just came about of its own volition..
I immediately zeroed in on the likely culprit XCode 4, but compiling the same project with 3.2.5 shows the same problem.
I'm rather flummoxed by this.. has anybody come across this weird phenomenon?
Best regards,
Frank
I`m used to iOS but you may have a similar issue. The UILabels have an "autoshrink" property, which reduces the font size if the text is too long, to avoid truncating it. You can turn this property off in the Interface Builder. Hope this helps!