Textfields in Tableview behave differently on iOS 9 and iOS10 - ios

My TableViewController uses auto-drawing custom cells with textfields and segmented controls. The textfields are selectable on iOS 10 and 11, and the keyboard pops up automatically. However, on iOS 9, the textfields returns no response upon tap, nor do the segmented controls. The app isn't frozen though, as everything else works just fine.
I'm using Xcode 9 and Swift 3.2. There's no error message from the console when textfields aren't responding on iOS 9.

the same thing happened to me... and the solution is..
select simulator.
go to hardware>>keyboard
then select all three opions and after that unselect those all.
thats it!!!
i thik this is the bug of simulator... but thats fix my problem.

Related

UITableView background black and empty cells black on iOS 8

Xcode 7.0b3
iOS Deployment Target 8.0
Here's the test app I made to isolate the issue.
Created a UITableViewController in a UINavigationController. Tap a cell, and pushes another one of those table view controllers. This table view controller has a random number of sections and rows in each section.
On iPhone running iOS 9, table scrolls correctly... empty cells are while.
On iPhone running iOS 8, table has black background. Empty rows are black instead of white.
In our "real" app, we sometimes see contents of old UITableView in a new UITableView. So I tried to isolate the issue to see if its a bug building with the Xcode 7 beta.
Does this sound like a bug building with the beta xcode and using iOS 8? Or did we create a bug/doing something wrong?
I had the same issue in Xcode 7 beta 3. Temporary workaround was to set tableView.backgroundColor = UIColor.whiteColor().
As of Xcode 7 beta 4 issue seems to be fixed.

iOS 8 with Xcode 6: PSCollectionView not scrollable and cell not selectable with Tabbed Application

I am using PSCollectionView, which is a Pinterest-style waterflow collection view. It is working very well with iOS 7 on Xcode 5&6 and in iOS 8 with Xcode 6, but in iOS 8 with Xcode 6 with TabBarController as the root controller, the view is not scrollable and cells are not selectable, just like the view is locked, even though it can load the data as normal.
I am wondering what may be the general reason for the collection view that is not scrollable and its cells are not selectable?
This class has already been 2-3 years, there may be some incompatibility within itself. For walking around, do you know there is any other Pinterest-style waterflow collection view that is working well now with iOS 8 with Xcode 6 that I can use instead?
Any ideas are appreciated! Thank you in advance!
After days trying to figure out this issue, finally got the solution.
It turns out it is nothing to do with the TabBar Controller nor iOS 8, it is the new setting of constraint of Xcode 6. I have to tick the "Installed" even though I already check "xC hR Installed" in the Attribute Inspector of the view used to show PSCollectionView. Now everything is working.
PS: but still don't know why I have to tick both of them to make it work. Any ideas?

UITableView black/crash iOS 8 - No Log

I'm building an app for iOS 7+ and I'm testing this on iOS 8 for now.
I'm creating a simple sign up form. Using a UITableView where one cell holds a UITextInput for the username and another cell underneath holds a UITextInput for password.
When I click on the username input field, the keyboard pops up as expected. Now, if I click on the password input field in the other UITableViewCell then the whole UITableView crashes/appears black. The keyboard remains visible however.
What's strange is that no logs are left either via the Terminal debug output area or the whole iPhone console log.
Additionally - this ONLY happens when running it on an actual iPhone. I cannot replicate the crash/black screen in the simulator (perhaps this is because the keyboard doesn't pop up in the simulator?). I'm using Xcode 6 beta 2 and building for iOS 7 and above. Running on iOS 8.
Lastly - I have stuck a debug output in prepareForReuse() for the respective cells. This does not get called.
Any tips on what is going on here?
Thanks in advance.
== Edit ==
After the "crash" the screen appears like (note: the status bar is hidden before the crash):
Disabling correction fixed the problem - how weird!

Xcode 5.1 iOS 7.1 problems with cells at UITableView

I think I have found serious bug in new release of Xcode 5.1 after update my cells start to disappeare when I scroll to the bottom.
When I press on them couple of them
When I scroll after that to the top everything is fine and this problem is only on iOS 7.1. At iOS 7.0.3 everything is works fine.
I have found a little hack to make it work at iOS 7.1 To do that I have download old version of Xcode(5.0.2) and make build of application that I have install at my device with iOS 7.1 in this case everything is works fine too. So I think it's some bug in Xcode 5.1
Im having the exact same problem with an app i was finalizing and things started to go crazy with the table views (all 3) right after the update..
found the solution
iOS 7.1 beta5 tableviewcell height showing objects outside it's range
add the following to your cell
cell.clipsToBounds =YES;
I also had the same problem when I opened my project in Xcode 5.1 but I solved it in Interface Builder (Storyboard).
Click on the Table View Cell (not the Content View or Table View).
In the Inspector, check 'Clip Subviews'.
Do the same for all the other Table View Cells of the Table View.

XCode 5 Table VIew Cell's Accessory -> Detail show nothing on iOS 6 device

I am migrating my app from iOS 6 to iOS 7. In XCode 5, I can see the Detail logo in the cell.
But, the reality is in iOS 6 device I can't see the Detail logo.
My App used to utilise Details Disclosure as accessory way. But, in iOS 7, it looks ugly. That is the reason I chosen Detail.
How to fix this?
Just use accessoryView, put any button you want there, and it will look the same on both iOS versions
You can also use the "detail disclosure" accessory instead of just using the "detail" accessory directly on your storyboard:
The down side of doing this is that it takes more space on the tableview in iOS 7 but the good one is you don't need add a custom button and you can attach segue from storyboard.

Resources