I am trying to ran my ios app using xcode 6 with ios8. On iOS8 ipad
splitview(basically master and detail screen) not rendering properly
but in ios7 it was able to render properly without any issues. The
issue was the maser view moved bit left since am seeing some unknown
images on right hand side of the master table view. This happens when i do change the orientation from portrait to landscape and vice verse.
Any idea how to fix this on ios8 ipad splitview?. For more info attaching screenshot
use this code in UITableViewController (or higher in hierarchy)
[[UITableViewCell appearance] setBackgroundColor:[UIColor whiteColor]];
Change the [UIColor whiteColor] to the color you want to replace the green with.
Setting background color for cell or content view in storyboard in Xcode does not solve the problem.
This problem occurs only on iPad under iOS 7.1.2 & 8.1 (i use these versions) and does not occur on iPhone (4S with iOS 8.1, 5S with 7.1.2, 6 with 8.1).
May be it happened in combination of Xcode 6.1 iOS 8.1 SDK and UISplitViewController.
Related
My app is supposed to run only on Iphone but apple is testing it on Ipad too. Apparently, the apps can run in Iphone mode on Ipads. How do I know which Ipad will run which Iphone mode (ex: ipad mini air2 = iphone 5 view settings in iphone mode?)?
How can I change the size of my UI based on changing aspect ratio programmatically ? (My views are created through code).
The iPad Pro runs an iPhone 6. The iPad 2 and Air 2 run an iPhone 4s.
I don't know if there's official documentation for this, but what I did is create a sample app and set the Devices to iPhone only. Then I added
print(self.view.frame.size) //Swift
NSLog(#"width = %f, height = %f", self.view.frame.size.width,
self.view.frame.size.height); //Obj-C
in the default ViewController. This will print the screen size of the view only, and not the entire iPad's screen. I then compared the printed value to the printed value of the same app run in iPhone 6/4s. You can try it too.
In terms of changing the size of your UI to fit different screen sizes, your best bet is probably AutoLayout. There are many (free, open source) frameworks available that make creating AutoLayout constraints programatically much simpler.
A few are Stevia, Cartography, SnapKit (Swift) / Masonry (Obj-C), or PureLayout.
As you said your app is supposed to run on iPhone only, then do the following process.
Select your project target in Xcode and goto General in which there is one section Deployment Info
Change the Devices to iPhone from dropdown
this will open app on iPhone only.
I am getting black screen on iOS 8 device.
Launch screen from LaunchScreen.storyboard works fine on iOS9 device.
I am pretty sure you did not need a launch image asset for iOS8 until I upgraded to Xcode 7
After much head banging, I found out that I had tried to attached a Cocou Touch file with my LaunchScreen View Controller. That was causing the problem. Once I removed the all outlet references from my launch screen, it started working in iOS 8.
I have iOS application since iOS 5, it includes a custom UITextView which use its own inputView and inputAccessoryView. It works with iOS 7 simulator, when it becomeFirstResponse, both inputView and inputAccessoryView show, but with iOS 8 simulator, only associated inputView shows, the inputAccessoryView does not show.
I am using Xcode 6 GM seed
HeInput_TextView.m
- (void)awakeFromNib
{
self.text = #"";
heKeyboard4x5 = [[HeKeyboard_ViewController alloc] init];
inputAccessoryVC = [[InputAccessory_ViewController alloc] init];
self.inputView = heKeyboard4x5.view;
self.inputAccessoryView = inputAccessoryVC.view;
}
Is it a bug in iOS 8 simulator or a change for iOS 8?
Edit:
I found more information about this problem.
This problem happens in Page-Based application, if an UITextView in a page of UIPageViewController, then the UITextView.inputAccessoryView doesn't show at iOS 8 simulator, but shows in iOS 7.1 simulator.
I creates two projects: 'Single-View Based application' and 'Page-Based application', and confirmed the problem happens as described above.
it is new behaviour of simulators in xcode 6. to see your custom accessory view or even default one try to uncheck hardware -> simulator -> connect harware keyboard.
It's an iOS8 bug.
You can reproduce it on the simulator in Apple's Contacts App.
Add a new contact and scroll down to "add a date".
Same problem. A colleague has raised an apple rdar.
I've found view accessories in iOS8 don't use the view's frame to offset their height above your InputView (or even the default software keyboard).
You might need to make sure your inputAccessoryView implements
-(CGSize)intrinsicContentSize
eg:
#implementation InputAccessory_View
// .. your code ...
-(CGSize)intrinsicContentSize{
return self.frame.size;
}
#end
My apologies, I misread the item. I've been driven batty by iOS8's keyboard issues.
In iPad i am using split view controller (one of my existing apps). Using Xcode 6 beta: If I launch the iPad simulator(s) with the device in portrait orientation it only shows the detail view and not the master view as well (and no "master" back button). If I rotate then to landscape all appears fine, rotate back to portrait and the "master"back button appears and can then access the master table view. With previous versions of Xcode the split view launches in portrait view.
I also noticed this, it seems to be a bug in Xcode 6 and iOS Simulator 8. You can send a bug report to Apple here
I had the same issue when running my app on the iOS8 simulator using xCode6-beta2. However, when I ran the app on my iOS7 device, the master view title showed up correctly. Sounds like an iOS8 issue.
I have an app that is working fine for iOS 5, I've just installed the iOS 6 simulator and my navigation is no longer working at all. Also my viewWillAppear and viewDidAppear methods are no longer firing.
I'm using [self.navigationController pushViewController:vc animated:YES]; to navigate. Do I have to use StoryBoards to navigate in iOS 6?
Thanks
No, Storyboards are optional and have been around since iOS 5.0. If your navigation is broken it'll be due to errors in your code.