ChatGPT解决这个技术问题 Extra ChatGPT

Warning frame for "Navigation bar" will be different at run time appears in Xcode 8 Swift 3

Before I've upgraded to Xcode 8 I haven't seen this error in such case. I have different Navigation Controllers. For all of them I see an error Frame for "Navigation bar" will be different at the run time. Navigation bar "Expected: width=384, Actual: width=375. In reality these Navigation Controllers doesn't have Navigation bar. Navigation bar exists for subviews. Anyway I could solve it by tick and untick the checkbox Shows navigation bar in Attributes inspector. But unfortunately every time I reopen Main.storyboard this warning appears again. Also if I click on yellow triangle and then on update frames nothing happen.

https://i.stack.imgur.com/6oRfI.png

Same issue here confirmed. None of the suggested resolutions fix the problem.
@GregP please check my solution and reply
@Ashish Kakkad please check my solution and reply
Filed rdar://28844288. Feel free to dupe openradar.me/radar?id=4985464104681472
This is my last warning that is bugging me after updating my project.

c
croxy

Warning will disappear if you change the property "Simulated Size" to "Freeform".

https://i.stack.imgur.com/tj9Nu.png


This doesn't solve problem. Close Xcode and Open again the issue will come again.
This is bugging the hell out of me.. I just tried this, and this does remove warning temporarily. You can always switch Simulated Size back and forth to remove the warning when it does come back. Super. Annoying.
Only a temporary fix - this is not the answer.
Either change this Simulated Size (and back to 'Inferred' or whatever) or "toggling Adjust Scrollview Insets on/off". Both will cause Storyboard to remove its misplaced="YES". This is an Xcode bug, and this fix is a force-refresh kind. Taken from @buildsucceeded answer.
@MobileBloke By force-refresh I meant that it will cause the Storyboard view to rewrite (refresh) the params, re-evaluate and remove the warning. It's really a refresh, force was only meant that it didn't do it automatically by itself (as it should) and needed some manual arbitrary change.
C
Community

As mentioned here you can fix this by toggling Adjust Scrollview Insets on/off.


Wow, and (checking git) literally all that happens when you do this is that misplaced="YES" gets removed. :/
That fixes it until the next time your close and reopen the project. Not a complete fix.
n
negersiu

I have changed from View as: iPhone 6S to iPhone 5S, then changed back to iPhone 6S, and Xcode did all the changes to remove the warning.


This worked for a short time- then after Xcode procesed it again - the same thing happened and the warning re-occured. Is this still working for you on latest Xcode?
g
guoc

This worked for me at Xcode 8.3.1 After restarting Xcode, it would still work.

https://i.stack.imgur.com/CxWu2.png

Select Navigation Controller

https://i.stack.imgur.com/A6gWW.png

Go to Show the Size Inspector

https://i.stack.imgur.com/Zm4bq.png

Change Simulated Size to Freeform

https://i.stack.imgur.com/48sTM.png

Change Simulated Size back to Fixed

https://i.stack.imgur.com/S8oAw.png

Then the warnings disappear.

https://i.stack.imgur.com/9S8vf.png


Any idea why this would have worked and not "Update frames" button?
@guoc, bro could you help me please stackoverflow.com/questions/46375778/… ?
J
Jensie

As a workaround just to get rid of the annoying warning I have been editing Main.storyboard manually by removing 'misplaced' in:

<navigationBar key="navigationBar" opaque="NO" contentMode="scaleToFill" misplaced="YES" translucent="NO" id="Os1-Xh-7XN">

A hack but it is nice to have zero warnings rather than 1 :)


Will I have to add this back later? I don't really care what my navigation Controller looks like so long as I don't have warnings. It's kind of funny. The storyboard recognizes the warning for a split second and then it goes away when you enter the storyboard this way.
I did the same thing and then don't touch the storyboard again. Everything works well.
PRoblem is that when you reload it comes back... anyone else noticing that it takes a long time to load the storyboard with the spinner running when this error occurs?
i
innesngunn

Click "View As" at the bottom left of your storyboard and choose a different device size, then click it again and swap back to the device size you started with. This worked for me.


it also just temp fixing it for me
n
nekonari

Until Xcode 8 is patched, you can set the "View as:" option to "iPhone SE" to eliminate the warning. Not ideal, but works for now.


I am USING SE .. but still Warning
Yeah, I know. But they do go away whenever you switch that selection to something else. Nowadays, I start with 7, switch to SE, then back to 7 to clear these warnings. Or just leave them, and just not check misplaced properties in when commiting changes.
U
UKDataGeek

I tried all the above suggestions but it didn't seem to work. I think it might be a more serious bug.

I have logged a bug with Apple Bug Reporter( link: https://bugreport.apple.com/logon) - if you want to do the same, then please reference bug : 31355220 so that Apple can tie it together. The more people that report it - the more information they will have to fix this annoyance.


t
templeman15

I was able to get rid of the issue completely by setting the simulated size of the view controller to freeform and then setting the width from 375 to 320.


You only need to set it only on the view controllers that have no parents (root view controller + maybe more, depending on what you have in your storyboard)
J
James Webster

Had the same issue, here's what I did to fix:

Expand the error information and click on the warning detail. Xcode should then automatically open the dimension/position settings. Replace the current value with the value suggested in the warning details.

https://i.stack.imgur.com/xtS0z.png

Basically, make sure that the size in your runtime is the same as the size you have specified in the size inspector.

You can also click the icon beside the image you posted (the yellow triangle with white circle. Sometimes, its a red circle icon) then there will be options to automatically fix/adjust the issues.

https://i.stack.imgur.com/OJyvB.png

I chose the update constraints option then adjusted the new constraints accordingly.


Does not work in this situation. The X/Y/Width/Height fields for the Navigation Bar are all grayed-out/uneditable.
@Ian Hmmm… I think I just ended up editing the xib so that the numbers matched up.
R
Radu Ursache

for me the problem was that i was hiding the bottom bar on push (using IB checkbox).

i had to select 'none' in 'bottom bar' option:

https://i.stack.imgur.com/S87Qq.png


G
GregP

Okay so it looks like I've fixed the issue. Here's what I did.

Select update frames like normal. Open a different file and then click back on the storyboard file. If that doesn't work then restart Xcode. It looks like it was updating internally but the interface builder UI was stuck as it sometimes gets.


After reopening of XCode this warning actually disappears, but if I open any file in the project an the again open main.storyboard these warnings appear again
A
Ash

Please change your device Preview in xcode for View controller and compile and check for warnings...

Xcode 8 is bit buggy, Interface builder reset its with random no which affects all contained views. Try changing your preview device.


C
ChuckZHB

Xcode 12

I think this problem is mostly because the width of device preview is different per various devices. E.g. iPhone 12 and iPhone 11 have different screenWidth. If you set a fix value on width of some view and give it some constraints, then it may not adopt your current previewed iPhone's screen width, so it complained "different size in run time".

And for me, I set an UIView and ImageView's width & height as fixed value in size inspector with iPhone 11 preview. And gives it also fixed 10 points leading and trailing constraints in IB. Then it complained if I switch to iPhone 12 preview.

To fix it, I select the viewController and chose "Update Frames". Then it looks better but Xcode still complain one conflict constraint after the change. Eventually, I manually found and fix it in IB.