I have old code using the MainWindow.xib, below iOS 7 everything works fine but in iOS 8 its leaving some bottom area.
Attaching image -
Please suggest anyone, how can i fix this.
I had this problem while ago. Turned out I had deleted the launch screen.
To make it right, add launch screen back by going in general setting of your project and adding your launch xib there.
I hope this fix your problem.
I solved this by adding new Launchimages. Removed my old ones and created a "New Launch Image". Also take a look at your autoresizing in the xib file under the "Size Inspector".
Related
I used XCode version 7.2.1 for my project. But I updated the XCode version 8.0 now. Though the scroll view is messed in view controllers of my project. Here I have used Resizing only not an Auto layout. I referred many forums. But can't able to find a solution for that. Here I have attached similar links to what I had tried.
Xcode 8 GM seed Storyboard layout issue
Layout issues after updating to Xcode 8
I have to update frame of everything in storyboard every time I start Xcode
What is the exact solution for Scroll view resizing issue in XCode version 8.0?
Its work for me
https://stackoverflow.com/a/39770664/6619234 you can try this...
after Save & Close don't open this xib/Storyboard....it is an temporary solution....till the apple fix it..
Apple just came out with XCode 8.2, which fixes this problem for me. I have been using XCode 7.3.1 for my interface design parallel to 8.1, but I can now use 8.2 without any problems.
The storyboard gets updated with widths and height of frames though, to accommodate the new 'View as:' functionality. Though it doesn't seem to affect running on device/simulator.
Curiously, the bugfix it is not noted in the XCode 8.2 release notes.
I was able to solve the same by selecting my xib files and then I selected my view in the xib after that I went to attribute inspector and changed the size, status bar, top bar and bottom bar as inferred and it worked but before that xocode pointed out I am missing 2x retina display file so I clicked the warning and it was added automatically.
I asked to Apple about this same issue, and they have sent the following message to my inbox:
Hello Raja,
Engineering has determined that your bug report (28489404) and will be closed.
I am trying to execute the steps described in iOS developer library basics tutorial. When I add "Scene to story board" run the simulator, I am not seeing the label. It is just white screen. Not sure what is causing this issue. Any suggestions?
Environment:
iOS SDK7.1
XCode 6.0
Rented server machine from MacInCloud.
EDIT:
Here is snap shot of my Xcode:
When I use "Single View Application" template, "Views" I am adding to story board are showing up properly in simulator.
It could be that the positioning of the label is outside of the visible screen. One quick way to rectify this would be to add a new Alignment Constraint so that the label is "Horizontal Center in Container". An example of how to add an Alignment Constraint below...
I thought to close this question first, but it seems not a good practice, so adding solution as answer.
I missed To configure the app delegate implementation file step from the documentation, which is why it is showing white screen. Make sure you delete the code which renders white background.
I have a question I am trying to create a database from a tutorial that I have posted on here. The problem that I keep having is that when I build the project the project is built successfully. However when the IOS simulator pulls up to show me the UI I have a black screen. I have doubled checked that my connections to my storyboards are correct. and still my UI still not displaying. I have made sure that I had my sqlite library connected within the project and it is. This is a single view application for an IPAD. I have searched ways of finding issues within my code and I have done breakpoints to see where my application breaks. and This is what I have found.
this is where my application breaks because is the first screen that it pops after I have started the IOS simulator. I do not know how to fix this.
this screen basically tells me that there is something wrong with the UIwindow alloc. For some reason is breaking here and I do not know why.
This last screen shot is not that great to interpret especially if its in numbers.
Please help. I will be posting more screen shots if needed at this point I need all the help that I can get. I did not think that it would be difficult to create and link a db.
If you are using storyboards you need to remove all the code in didFinishLaunchingWithOptions and just return YES. Also set your main storyboard file appropriately in the plist file.
In my app I have set custom image for segment control. Image shows up very well on the simulator but not on the device. I checked all possible ways and tried what ever was answered for this issue earlier for the issues same as I have now. But still I can't locate exact solution for this. Can anyone help please.
Did you try removing/readding the image? As far as I know, the simulator has its own cache, if the image has been removed somehow, that may be why its showing up.
You may try:
Remove the image from xcode, and re-adding it
Making a clean build
Remove the image from "bundle resources", (see: https://stackoverflow.com/a/12741872/936957) and readding it
Quitting / restarting xcode
One of them should help
So I am working on an app https://github.com/Kronusdark/PerlinNoiseKit and I had a (crappy) iPhone UI going, but I decided to make it run on my iPad. The problem is that when it loads the iPad storyboard, I get a black screen. I have checked my project summary and it is pointing to the correct storyboard file. The outlets all appear to be set correctly, and it will actually run code in my viewController on my iPad. I just get no UI. I have pushed my most recent changes to my repo if anyone wants to try to run it, any advice would be helpful.
Eureka! It turns out one of my sub-views were not working properly. After I removed the offending view my storyboard loaded no problem. I believe it was due to a rogue drawRect:.